Borrowing it
Nothing to install: this file belongs to GRACENOBLE/fullstack-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GRACENOBLE/fullstack-template/main/.claude/commands/implement.mdgit clone --depth 1 https://github.com/GRACENOBLE/fullstack-templateWrote 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/gracenoble/fullstack-template/implement)<a href="https://agentmods.dev/commands/gracenoble/fullstack-template/implement"><img src="https://agentmods.dev/badge/commands/gracenoble/fullstack-template/implement/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/commands/gracenoble/fullstack-template/implement"><img src="https://agentmods.dev/badge/commands/gracenoble/fullstack-template/implement.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.00000 | $0.00375 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- implement — 100% identical, 0 lines differ
What it actually says
Implement a feature following the Documentation-First workflow. This ensures every implementation is grounded in existing patterns and leaves the docs in a better state than it found them.
Required from user before starting
- Feature description (what it does, which layer — backend / web / both)
- Any constraints or decisions already made
Step 1 — Documentation check
Delegate to the docs agent:
"Check existing documentation relevant to [feature]. Read _index.md for both apps, find the relevant topic docs, compare them against their source files, and report: which docs are current, which are stale, and what's missing."
Wait for the report before proceeding.
Step 2 — Assess and decide
Based on the docs agent report:
| Situation | Action |
|---|---|
| Docs match code | Proceed to Step 3 |
| Docs are stale | Fix the stale docs first (delegate to docs agent), then Step 3 |
| No docs exist | Note it — new docs will be created in Step 4 |
Do not implement against stale documentation. Update docs first.
Step 3 — Implement
Delegate to the appropriate agent (backend, web, or both).
Pass the relevant doc content as context so the agent implements to the correct patterns — not from training data.
Run /project:check at the end of this step. Do not proceed if it fails.
Step 4 — Update documentation
Delegate to the docs agent:
"Update documentation to reflect the implementation of [feature]. Files changed: [list files]. Update last_verified dates. Create new topic doc if a new topic was introduced."
Step 5 — Summary
Report:
- What was implemented
- Which docs were updated or created
- Output of
/project:check
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 · 56 lines · 0 tokens per session scan A 45ab18d1ec6e
implement is a command published in the GitHub repository GRACENOBLE/fullstack-template (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 375 tokens. 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-09-04.
Other commands, from other repositories
review-diff
Round 1 review - fan out correctness, security, and invariant lanes over a git range and write local://review-findings.md.
fix-findings
Triage and fix the open rows in local://review-findings.md, classifying every one as fixed, wont-fix, or invalid.
review-fixes
Round 2 review - verify each finding is actually resolved and hunt regressions introduced by the fixes.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.