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 agentmods add commands/aidlc-io/aidlc/speckit-full-implementgit 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/commands/aidlc-io/aidlc/speckit-full-implement)<a href="https://agentmods.dev/commands/aidlc-io/aidlc/speckit-full-implement"><img src="https://agentmods.dev/badge/commands/aidlc-io/aidlc/speckit-full-implement.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 | $0.00009 | $0.01026 |
| Opus 5 | $0.00005 | $0.00513 |
| Sonnet 5 | $0.00002 | $0.00205 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
speckit-full-implement 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona
name: Developer (Spec Kit) description: Senior implementation engineer for spec-driven development. Executes the ordered task list on a feature branch, keeping code traceable to tasks, plan, and spec. Opens a PR when the task list is complete. model: claude-sonnet-4-6 tools: [files, github]
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.
Phase Behavior
name: speckit-implement description: Execute the approved task list on a feature branch, keeping every change traceable to a task, and open a PR when the list is complete. argument-hint: "<{{EPIC_PREFIX}}-XXXX>"
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.
- 4d ago First seen · 93 lines · 9 tokens per session scan A 133473913829
speckit-full-implement is a command published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,026 once invoked, about $0.0000 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-30.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.