See it in action
A filled API-surface input/output contract from a two-request HAR fixture
The author supplies an exact request and populated response: two records form one numeric-path group with 200/404 statuses, coverage, source digests and explicit inference/body-byte limitations. This is a fixture contract example, not live API evidence.
Example input
{
source: {
kind: "retained-evidence",
evidence_id:
"ev_90073e9478eada1e2cc351b523e6ba9231c9b4bc9708773567b880094db9d4c7",
},
view: {
kind: "api-surface",
offset: 0,
limit: 50,
},
}Example output
{
parent_evidence_id:
"ev_90073e9478eada1e2cc351b523e6ba9231c9b4bc9708773567b880094db9d4c7",
parent_operation: "inspect_web_network_capture",
parent_digest:
"90073e9478eada1e2cc351b523e6ba9231c9b4bc9708773567b880094db9d4c7",
view_digest:
"c9494341920dc4cff6ecc6d8ed2c5e3abf15976642c253248e220d45f290ca7b",
artifact: {
path: "/fixtures/api-surface.har",
sha256:
"bf58e2c06e55bfe7e0628157c4ad027ce0aeb81a10e8edef8a7f95b8e5f14225",
},
coverage: {
status: "page",
examined: 1,
total: 1,
next_offset: null,
exhausted: true,
},
limitations: [
"Grouping does not establish handler identity, URL-space schemas or causality.",
"HAR text is producer-decoded Unicode. Original body bytes remain unknown unless content explicitly uses valid base64; declared sizes are preserved independently of retained bytes. mitmproxy 12.2.3 SaveHar may report null optional postData.text; that null is retained and omitted only from the upstream validation copy.",
],
unknowns: [],
records: {
examined: 2,
total: 2,
excluded: 0,
},
templated_groups: 1,
groups: [
{
method: "GET",
origin: "https://api.example.test",
path_template: "/users/{numeric}",
templated_segments: [
{
segment_index: 1,
rule: "numeric",
basis: "inferred",
observed_values: ["8812", "9031"],
},
],
record_ordinals: [0, 1],
statuses: [200, 404],
content_types: ["application/json", "text/plain"],
flags: ["mixed-statuses", "mixed-content-types"],
},
],
excluded_records: [],
kind: "api-surface",
view: {
kind: "api-surface",
offset: 0,
limit: 50,
},
}License
Exact input and output object literals extracted from the author module. Its comment says the example was generated through the HAR decoder and view service; that generation was not reproduced here. Fixture paths and retained Evidence IDs belong to this example, not a live site session. All output limitations are preserved. The fragments depend on project contract context and are not standalone programs.
MIT License
Copyright (c) 2026 morluto
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/morluto/rea --skill rea-tool-designBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
REA tool design
Use the tool-design guide for tool boundaries, contract semantics, provider ownership, and discoverability. Inspect the current contract and nearest existing tool relevant to the analyst question; source, documentation, and live catalogs may describe different versions.
For provider-backed work, exercise the analyst's task through REA and compare relevant native provider and independent artifact observations where available. Check applicable partial results, recovery and session boundaries; report what was not exercised. Use workflow verification to select evidence for the proposed contract instead of seeking provider API parity.
For an audit, follow audit existing tools: scope representative tasks, exercise the live workflow, and distinguish reproduced bugs, supported limitations, design opportunities and unverified claims. Report working alternatives and evidence limits as well as findings.
For a design request, return the proposed boundary, input/result shape, Evidence semantics, nearest alternative, and verification approach. Implement when requested, preserving the user's scope and existing authorization.
For implementation or verification, consult testing for the affected consumer and provider lanes, and contributing for generated-file ownership. Read provider/workflow guides only as the task requires.
