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 skills add stepanenkoviktor0110-boop/ai-dev-methodology-codex --skill code-writinggit clone --depth 1 https://github.com/stepanenkoviktor0110-boop/ai-dev-methodology-codexWrote 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/skills/stepanenkoviktor0110-boop/ai-dev-methodology-codex/code-writing)<a href="https://agentmods.dev/skills/stepanenkoviktor0110-boop/ai-dev-methodology-codex/code-writing"><img src="https://agentmods.dev/badge/skills/stepanenkoviktor0110-boop/ai-dev-methodology-codex/code-writing.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.1 | $0.00077 | $0.03526 |
| Opus 5 | $0.00039 | $0.01763 |
| Sonnet 5 | $0.00015 | $0.00705 |
| Haiku 4.5 | $0.00008 | $0.00353 |
Grade A, and why
code-writing 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 7d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 161 lines · 77 tokens per session scan A 2746b161b9fb
code-writing is a skill published in the GitHub repository stepanenkoviktor0110-boop/ai-dev-methodology-codex (1 stars, last pushed 4mo ago), with no licence file. It adds 77 tokens to every session and 3,526 once invoked, about $0.0004 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 skills, from other repositories
tdd-workflow
A test-first development workflow, commonly called TDD, where a failing test is written before the code that should make it pass. The cycle then adds the smallest working change and cleans it up.
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code. Enforces red-green-refactor cycle with strict rules.
spec-driven-task-decomposer
Use this skill when approved requirements and design need to be decomposed into tasks.md for Phase 3 of a Spec-Driven change. It creates atomic, traceable implementation and testing tasks, validates the plan, and should not be used to design architecture or write implementation code.
joycraft-implement
Execute atomic specs with TDD — read spec, write failing tests, implement until green, wrap up and continue the queue.
test-writer
Write thorough tests following TDD and BDD principles.
joycraft-implement-level5
Invoked by tune's roadmap or the human opting into Level 5 — set up the autofix loop, holdout scenario testing, and scenario evolution from specs.