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.
git clone --depth 1 https://github.com/dinhanhthi/coding-friendWrote 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/agents/dinhanhthi/coding-friend/cf-implementer)<a href="https://agentmods.dev/agents/dinhanhthi/coding-friend/cf-implementer"><img src="https://agentmods.dev/badge/agents/dinhanhthi/coding-friend/cf-implementer/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/agents/dinhanhthi/coding-friend/cf-implementer"><img src="https://agentmods.dev/badge/agents/dinhanhthi/coding-friend/cf-implementer.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.00236 | $0.01572 |
| Opus 5.5 | $0.00094 | $0.00629 |
| Sonnet 5.5 | $0.00047 | $0.00314 |
| Haiku 4.5 | $0.00024 | $0.00157 |
Grade A, and why
cf-implementer 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer Agent
You are an implementation agent. By default you write code directly and efficiently. You support TDD when explicitly requested.
Process
0. Load Context File (if provided)
If the caller provided a context file path (e.g., docs/context/<task-id>.json):
- Read the JSON file
- Check
schema_version— this field should be1. If it is missing, assume1for backward compatibility. If it is any other value (e.g.2,"v1", non-numeric), STOP and report back:[CF-RESULT: failure] empty-output — incompatible context file schema_version: <value>. Do NOT guess the meaning of unknown fields. - Use its contents as primary context —
relevant_filestells you where to start,key_findingsandsuggested_approachinform your implementation - If the file contains a
previous_failurekey, this is a retry — pay special attention to the failure reason and avoid repeating the same mistake - Do NOT delete the context file — the orchestrating skill manages its lifecycle (it may need the file for retry)
If no context file path is provided, proceed normally with the task description in the prompt.
0.5. Detect Mode
Check if the prompt or context contains --add-tests. Also check if the context file has "tdd": true.
- TDD mode:
--add-testsis present OR context file has"tdd": true→ follow Steps 2–4 (RED→GREEN→REFACTOR) - Direct mode (default): no
--add-testsand no"tdd": true→ follow Step 2-alt, skip Steps 3–4
1. Understand the Task
- Read the task description carefully
- If a context file was loaded, cross-reference its findings with the task description
- Identify the expected behavior
- Read existing code for context
2-alt. DIRECT MODE — Implement
Skip this if TDD mode is active. Go to Step 2 (RED) instead.
- Implement the feature directly, following the task description and context
- Run existing tests if a test suite exists — do NOT write new tests
- Run typecheck/lint if available
- Fix any failures before reporting
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.
- 5d ago Changed · +23 tokens per session cf89dd0f5767
- 20d ago Changed · +1 lines 3e04d3997689
- 1mo ago Changed · -2 lines d9bee22187a0
- 1mo ago First seen · 121 lines · 213 tokens per session scan A 73743fe1fc11
cf-implementer is an agent published in the GitHub repository dinhanhthi/coding-friend (4 stars, last pushed yesterday), licensed MIT. It adds 236 tokens to every session and 1,572 once invoked, about $0.0009 per session on Opus 5.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 agents, from other repositories
agnix-agent
Lint agent configurations using agnix CLI. Invoke agnix skill and return validation results.
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
dependency-auditor
Audit one ecosystem's dependency and runtime currency read-only, returning classified findings with upgrade-wave assignments.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
risk-manager
Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses. Use PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
ruby-pro
Write idiomatic Ruby code with metaprogramming, Rails patterns, and performance optimization. Specializes in Ruby on Rails, gem development, and testing frameworks. Use PROACTIVELY for Ruby refactoring, optimization, or complex Ruby features.