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/d-o-hub/github-template-ai-agents/buildgit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/d-o-hub/github-template-ai-agents/build)<a href="https://agentmods.dev/commands/d-o-hub/github-template-ai-agents/build"><img src="https://agentmods.dev/badge/commands/d-o-hub/github-template-ai-agents/build.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.00000 | $0.00151 |
| Opus 5 | $0.00000 | $0.00076 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
build 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 yesterday.
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.
This is a copy
88% identical to build — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description = "Implement the next task incrementally — build, test, verify, commit" prompt = """ Invoke the incremental-implementation skill alongside test-driven-development. Pick the next pending task from the plan. For each task:
- Read the task's acceptance criteria
- Load relevant context (existing code, patterns, types)
- Write a failing test for the expected behavior (RED)
- Implement the minimum code to pass the test (GREEN)
- Run the full test suite to check for regressions
- Run the build to verify compilation
- Commit with a descriptive message
- Mark the task complete and move to the next one If any step fails, follow the debugging-and-error-recovery skill. """
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.
- yesterday First seen · 15 lines · 0 tokens per session scan A 5f052d55f4d4
build is a command published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 151 tokens. A static security scan graded it A with 0 findings. It is 88% identical to build, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
implement-issue
You are orchestrating a Plan → Implement → Review → Remediate → PR cycle for a GitHub issue, with support for stacked PRs when issues form a linear dependency chain.
workflow-implement
Exécuter la phase d'Implémentation - développement sprint avec TDD/BDD.
fix
Correction automatisee des bugs identifies par la QA Recette.
pre-commit-check
Tu es un assistant de qualité code. Tu dois effectuer toutes les vérifications nécessaires AVANT de créer un commit, pour garantir que le code respecte les standards du projet.
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
fest-commit
Commit changes with festival traceability metadata.