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 kaisa-kucherenko/claude-code-flow --skill implementgit clone --depth 1 https://github.com/kaisa-kucherenko/claude-code-flowWrote 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/kaisa-kucherenko/claude-code-flow/implement)<a href="https://agentmods.dev/skills/kaisa-kucherenko/claude-code-flow/implement"><img src="https://agentmods.dev/badge/skills/kaisa-kucherenko/claude-code-flow/implement/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/skills/kaisa-kucherenko/claude-code-flow/implement"><img src="https://agentmods.dev/badge/skills/kaisa-kucherenko/claude-code-flow/implement.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.00140 | $0.04157 |
| Opus 5.5 | $0.00056 | $0.01663 |
| Sonnet 5.5 | $0.00028 | $0.00831 |
| Haiku 4.5 | $0.00014 | $0.00416 |
Grade A, and why
implement scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Read, Grep, Glob, Write, Edit, Agent, Bash(git log:*), Bash(git status:*), Bash(git diff:*), Bash(ss:*), Bash(curl:*), Bash(setsid python3 -m http.server:*) How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement — run one phase of a spec
The spec says what; this skill is how a phase moves from text to a commit without the user losing the thread. One invocation = one phase.
Prerequisites
A Linux or macOS shell with ss (or lsof — adjust the port checks), setsid, and a scripted
browser (playwright) for browser rows. <scratchpad> is the session's temporary directory —
any per-session temp path works, it only has to survive the phase. The project's CLAUDE.md
must name its stack start command, its ports, its health endpoint and its test/lint/build
commands: this skill runs them, it does not guess them.
0. Which phase — the handoff decides
Main flow (/implement, no number): read the live handoff (HANDOFF_*.md in the project
root; several → the one whose topic matches the current branch/issue). Its NEXT names
the next phase and the spec path; the handoff's done-section («Зроблено» in a Ukrainian
handoff — the heading follows the handoff's language) lists the phases already committed. If
NEXT does not name the spec path, look in the handoff's Artifacts section; still nothing →
ask before launching, do not guess. Cross-check against the spec index's phase map and
git log on the branch — a phase marked done in the handoff but absent from the log (or the
reverse) is a divergence: say so, stop.
Spec index = the single spec file (<topic>-spec.md) or the directory's README.md —
whichever the spec has; it carries the preamble, the Ground rules and the phase map, and it is
where a phase gets marked done (step 7).
Alternative (/implement N): the user names the phase. Still read the handoff for the spec
path and the done-list; if N's dependencies are not done, say so, stop.
No handoff → the spec index's map is the only source; say that the handoff is missing and offer /handoff before continuing.
Spec location: the path in the handoff; else <topic>-spec.md or <topic>-spec/README.md
next to the ADR (project root, or docs/adr/<domain>/ for a split ADR). Phase file: NN-<name>.md or the ## Phase N section.
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.
- 1mo ago First seen · 244 lines · 140 tokens per session scan A a6329734eb94
implement is a skill published in the GitHub repository kaisa-kucherenko/claude-code-flow (23 stars, last pushed 4d ago), licensed MIT. It adds 140 tokens to every session and 4,157 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-19.
Other skills, from other repositories
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
verify-akashic-plugin
A plugin acceptance skill that commits a plugin, installs it into the running application, checks its status, and uses it once to confirm whether it works.
coverage-drop-investigator
Use when test coverage has dropped and you need to find which changes caused it and what tests to add. Traces coverage regressions to specific commits and files.
Changelog Test Mapper
Map changelog entries and release notes to affected test cases, ensuring every user-facing change has corresponding test coverage verification.