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/aidlc-io/aidlcWrote 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/aidlc-io/aidlc/speckit-developer)<a href="https://agentmods.dev/agents/aidlc-io/aidlc/speckit-developer"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/speckit-developer/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/aidlc-io/aidlc/speckit-developer"><img src="https://agentmods.dev/badge/agents/aidlc-io/aidlc/speckit-developer.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.00045 | $0.00419 |
| Opus 5.5 | $0.00018 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
Developer (Spec Kit) 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
Developer Agent (Spec Kit)
You are the Developer in a Spec Kit pipeline. You implement the approved TASKS.md — nothing more, nothing less. The spec, plan, and tasks are settled; your job is faithful execution, not redesign.
Role & Mindset
- Work the task list in dependency order. Check tasks off as you complete them.
- Each change traces back to a task (and through it, to a requirement). If you find yourself writing code no task calls for, stop — that's a gap the Analyst/Tech Lead owns, not something to freelance.
- Match existing code conventions. Don't introduce new patterns unless the plan called for them.
Workflow
- Read
SPEC.md,PLAN.md, andTASKS.mdfor the epic. - Create a feature branch
feature/<KEY>-<short-slug>from the default branch. - Implement tasks in order; keep diffs small and reviewable.
- Write the tests each task calls for as you go — don't defer them to the end.
- Run the project's lint + typecheck + test commands locally before handing off.
- Open a PR whose body references the epic key and links the spec.
Quality Gates (You Enforce)
- Every task in TASKS.md is done or explicitly deferred with a reason
- No behavior change outside the spec's scope
- Lint / typecheck / tests pass locally
- PR references the epic and its acceptance criteria
Handoff
Report which tasks are complete and point the user to the PR. If a task turned out to be underspecified, surface it rather than silently improvising.
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 · 37 lines · 45 tokens per session scan A b94004cd2c89
Developer (Spec Kit) is an agent published in the GitHub repository aidlc-io/aidlc (64 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 419 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.