dev-implement

A development command for the Coacoa framework, which checks the files needed to implement a development story before following the developer instructions.

In plain words
What is it for?
Use it to implement a story according to the framework’s methodology and validate code references.
Why use it?
It prevents implementation from proceeding when the framework, story template, or quality checks are unavailable.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/im-shashanks/coacoa/dev-implement
Clone the repo
git clone --depth 1 https://github.com/im-shashanks/CoaCoA

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 240 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00240
Opus 5 $0.00000 $0.00120
Sonnet 5 $0.00000 $0.00048
Haiku 4.5 $0.00000 $0.00024

Measured yesterday against content hash 57306c5d7b60, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev-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 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.

src/coacoa/scaffold/ide_helpers/.claude/commands/dev-implement.md · 16 lines

What it actually says

THIS COMMAND IS FOR DEVELOPMENT IMPLEMENTATION. YOU MUST FOLLOW INSTRUCTIONS EXACTLY AS GIVEN. DO NOT DEVIATE FROM THE PROCESS.

MANDATORY PRE-EXECUTION CHECKLIST

Before executing this command, CONFIRM these files exist and are readable:

  • coacoa/coacoa.yaml (framework configuration)
  • coacoa/agents/dev.md (agent instructions)
  • coacoa/tasks/implement_story.md (implementation methodology)
  • coacoa/templates/story.md (story template with micro-context)
  • coacoa/quality/anti_hallucination.md (validation checklist)
  • coacoa/quality/link_integrity.md (code reference validation)

IF ANY FILE IS MISSING: Stop and report "❌ VALIDATION FAILED: Framework not properly installed - run 'coacoa init' first" ONLY PROCEED if all framework files confirmed present.

INSTRUCTION

As a dev agent you MUST follow the instructions EXACTLY as in Path: coacoa/agents/dev.md

Changes

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.

  1. yesterday First seen · 16 lines · 0 tokens per session scan A 57306c5d7b60

Subscribe to this mod's changes

dev-implement is a command published in the GitHub repository im-shashanks/CoaCoA (5 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 240 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-08-31.