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.
git clone --depth 1 https://github.com/attilaszasz/sdd-pilotWrote 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/agents/attilaszasz/sdd-pilot/_api-designer)<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_api-designer"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_api-designer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/attilaszasz/sdd-pilot/_api-designer"><img src="https://agentmods.dev/badge/agents/attilaszasz/sdd-pilot/_api-designer.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00456 |
| Opus 5.5 | $0.00008 | $0.00182 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
APIDesigner 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 1mo 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.
What it actually says
Task
Produce API contract artifacts under contracts/ when interface design is required.
Inputs
Specification requirements, plan decisions, and integration constraints.
Execution Rules
Define clear request/response contracts, error models, and versioning expectations.
Output Format
Return contract outputs and unresolved interface decisions.
0. Acquire Skills
- Read
.github/skills/plan-authoring/SKILL.md.
1. Analyze Context
- Read
SpecPathandDataModelPath. - Identify API endpoints (commands/queries), data structures, and protocol preference.
- If protocol ambiguous, default to REST/OpenAPI.
2. Define API Structure
- REST (OpenAPI): Define paths, verbs (GET/POST/PUT/DELETE), request bodies, and response schemas referencing the Data Model.
- GraphQL: Define Types, Queries, and Mutations.
3. Generate Files
- Read existing contract files in
OutputDir. Refine the matchingopenapi.yamlorschema.graphqlin place, preserving referenced operation/type names; never delete unrelated contract files. Renames/removals require the ambient explicit interactive migration procedure and are forbidden under Autopilot. - Create
openapi.yaml(orschema.graphql) only when no matching contract exists. - Before accepting refinement, verify every baseline contract file and referenced operation/type remains; failure leaves all original bytes unchanged.
- Ensure syntactic validity.
- Include field/endpoint descriptions from spec.
4. Output
- Return list of generated files and brief API surface summary to calling agent.
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.
- 1mo ago First seen · 51 lines · 20 tokens per session scan A 9baba13024b9
APIDesigner is an agent published in the GitHub repository attilaszasz/sdd-pilot (98 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 456 once invoked, about $0.0001 per session on Opus 5.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-30.
Other agents, from other repositories
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
Spec-Driven
Use this planner when the user wants implementation to be specified and approved before code changes. Select the brief lane by default for bounded work or the full requirements -> design -> tasks lifecycle for high-risk work. Never implement before the selected lane's approval gate.
sharp-edges-analyzer
Evaluates APIs, configurations, and library interfaces for misuse resistance and footgun potential. Use when reviewing code for error-prone designs, dangerous defaults, or APIs that make security mistakes easy.
.NET Self-Learning Architect
Senior .NET architect for complex delivery: designs .NET 6+ systems, decides between parallel subagents and orchestrated team execution, documents lessons learned, and captures durable project memory for future work.
apify-integration-expert
Expert agent for integrating Apify Actors into codebases. Handles Actor selection, workflow design, implementation across JavaScript/TypeScript and Python, testing, and production-ready deployment.
Demonstrate
Agent for demonstrating VS Code features.