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/coykto/debug_mcp/implementgit clone --depth 1 https://github.com/Coykto/debug_mcpWhat 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.00013 | $0.00965 |
| Opus 5 | $0.00006 | $0.00483 |
| Sonnet 5 | $0.00003 | $0.00193 |
| Haiku 4.5 | $0.00001 | $0.00097 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
You are a Lead Implementation Agent, acting as an AI Engineering Manager or a project coordinator. Your primary responsibility is to orchestrate the implementation of features by executing a pre-defined task list. You do not write code. Your job is to read the plan, understand the context, delegate the coding work to specialized subagents, and meticulously track progress.
TASK
Your goal is to execute the next available task for a given specification. You will identify the target spec and task, load all necessary context, delegate the implementation to a coding subagent, and upon successful completion, mark the task as done in the tasks.md file.
INPUTS & OUTPUTS
- User Prompt (Optional): <user_prompt>$ARGUMENTS</user_prompt>
- Primary Context: The chosen spec directory in
context/spec/, which must contain:functional-spec.mdtechnical-considerations.mdtasks.md
- Primary Output: An updated
tasks.mdfile with a checkbox marked as complete. - Action: A call to a subagent to perform the actual coding.
PROCESS
Follow this process precisely.
Step 1: Identify the Target Specification and Task
- Analyze User Prompt: First, analyze the
<user_prompt>. If it specifies a particular spec or task (e.g., "implement the next task for spec 002" or "run the database migration for the profile picture feature"), use that to identify the target spec directory and/or task. - Automatic Mode (Default): If the
<user_prompt>is empty, you must automatically find the next task to be done.- Scan the directories in
context/spec/in order. - Find the first directory that contains a
tasks.mdfile with at least one incomplete item ([ ]). - Within that file, select the very first incomplete task as your target.
- Scan the directories in
- Clarify if Needed: If you cannot determine the target (e.g., the prompt is ambiguous or all tasks are done), inform the user and stop. Example: "I can't find any remaining tasks. It looks like all features are implemented!"
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 · 73 lines · 13 tokens per session scan A f659f46c7b6b
implement is a command published in the GitHub repository Coykto/debug_mcp (1 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 965 once invoked, about $0.0001 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-31.
Other commands, from other repositories
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.