Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add nek1987/auto-agent-harness --skill api-designergit clone --depth 1 https://github.com/nek1987/auto-agent-harnessWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nek1987/auto-agent-harness/api-designer)<a href="https://agentmods.dev/skills/nek1987/auto-agent-harness/api-designer"><img src="https://agentmods.dev/badge/skills/nek1987/auto-agent-harness/api-designer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00077 | $0.03455 |
| Opus 5 | $0.00039 | $0.01728 |
| Sonnet 5 | $0.00015 | $0.00691 |
| Haiku 4.5 | $0.00008 | $0.00346 |
Grade A, and why
api-designer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/graphql_schema.graphql 8.4 KB
- examples/openapi_spec.yaml 18 KB
- README.md 2.1 KB
- references/authentication.md 11 KB
- references/common-patterns.md 12 KB
- references/rest_best_practices.md 15 KB
- references/versioning-strategies.md 14 KB
- scripts/api_helper.py 14 KB runs code
- skill-report.json 9.9 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 559 lines · 77 tokens per session scan A 6db6374d77b6
api-designer is a skill published in the GitHub repository nek1987/auto-agent-harness (5 stars, last pushed 5mo ago), with no licence file. It adds 77 tokens to every session and 3,455 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
api-debugging
Systematic approach to debugging REST APIs, HTTP errors, authentication issues, and network problems. Use when the user has API errors, status code issues, timeout problems, or needs help troubleshooting HTTP requests.
api-design-reviewer
Use when reviewing a PR that adds or changes API endpoints, auditing an existing API for v2 migration, or establishing REST API standards. Triggers on "API review", "REST design review", "breaking change check", "OpenAPI audit", "endpoint review", or "API consistency".
add-api-endpoint
Use when a ticket asks to add or extend an HTTP/API endpoint — a new route, handler, or RPC method — with request validation and a defined response. Invoke for "add a POST /things endpoint", "expose a list API", or "add a field to the X response".
backend-service
Use when a ticket asks for backend business logic that isn't itself an endpoint or a migration — a service/use-case, a domain operation, a background job, or orchestration across repositories. Invoke for "add a service to do X", "implement the use-case", or "extract the business logic out of the handler".
doc-generator
Auto-generate API reference documentation from Python code.
claude-api
Use this skill when the user is building against Anthropic APIs or SDKs, including @anthropic-ai/sdk, anthropic, or Agent SDK integrations.