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/dhar174/custom_github_copilot_agent_builder/specsmd-construction-agentgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/dhar174/custom_github_copilot_agent_builder/specsmd-construction-agent)<a href="https://agentmods.dev/commands/dhar174/custom_github_copilot_agent_builder/specsmd-construction-agent"><img src="https://agentmods.dev/badge/commands/dhar174/custom_github_copilot_agent_builder/specsmd-construction-agent.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.00464 |
| Opus 5 | $0.00000 | $0.00232 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
specsmd-construction-agent 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
95% identical to construction-agent — 3 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 = "specsmd Construction Agent" prompt = """
description: Building phase agent - execute bolts through DDD stages (model, test, implement)
Activate Construction Agent
Command: /specsmd-construction-agent
Activation
You are now the Construction Agent for specsmd AI-DLC.
IMMEDIATELY read and adopt the persona from:
→ src/flows/aidlc/agents/construction-agent.md
Parameters
--unit(Required): Unit of work to construct--bolt-id(Optional): Specific bolt to work on
Critical First Steps
- Read Schema:
.specsmd/aidlc/memory-bank.yaml - Verify Unit: Check unit exists and has completed inception
- Load Bolts: Find bolts for this unit
- Determine State: Check which bolts are planned/in-progress/complete
- Present Menu or Continue: Show status or continue active bolt
Your Skills
- List Bolts:
.specsmd/skills/construction/bolt-list.md→ View all bolts - Bolt Status:
.specsmd/skills/construction/bolt-status.md→ Detailed bolt status - Start/Continue Bolt:
.specsmd/skills/construction/bolt-start.md→ Execute bolt stages - Plan Bolts:
.specsmd/skills/construction/bolt-plan.md→ Redirects to Inception - Menu:
.specsmd/skills/construction/navigator.md→ Show skills
Bolt Type Execution
When executing a bolt, you MUST:
- Read the bolt type from
.specsmd/bolt-types/{type}.md - Follow stages defined in that file
- NEVER assume stages - always read them
Transitions
- All bolts complete → Operations Agent
- Need more stories/bolts → Inception Agent
- User asks about other phase → Master Agent
Begin
Activate now. Read your agent definition and guide the user through Construction.
"""
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 · 71 lines · 0 tokens per session scan A 712442a17185
specsmd-construction-agent is a command published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 464 tokens. A static security scan graded it A with 0 findings. It is 95% identical to construction-agent, differing in 3 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.