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 leechen298/Code2Skill --skill code2skill-review-flowgit clone --depth 1 https://github.com/leechen298/Code2SkillWrote 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/leechen298/code2skill/code2skill-review-flow)<a href="https://agentmods.dev/skills/leechen298/code2skill/code2skill-review-flow"><img src="https://agentmods.dev/badge/skills/leechen298/code2skill/code2skill-review-flow/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/leechen298/code2skill/code2skill-review-flow"><img src="https://agentmods.dev/badge/skills/leechen298/code2skill/code2skill-review-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.02235 |
| Opus 5.5 | $0.00013 | $0.00894 |
| Sonnet 5.5 | $0.00006 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
code2skill-review-flow 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code2Skill Main Flow Review
The complete Chinese version is available at references/SKILL.zh-CN.md.
Follow the user's language for the final reply, review conclusions, and all user-facing content.
Review whether an existing Code2Skill-generated package can help an Agent complete the main user goals along representative standard paths. This Skill answers only whether the main flows are basically usable; it does not prove field by field that the generated package fully matches the source code.
This Skill is read-only, offline, and source-first by default. It may be used by an independent Agent or invoked separately after code2skill-generate completes. It does not generate Contracts, evidence matrices, review reports, or other deliverable files.
Inputs and Boundaries
Before starting, determine:
- the path of the generated package to review;
- the source roots and page, directory, interface, or feature scope explicitly authorized by the user;
- whether only some main goals should be reviewed;
- whether the user has also authorized fixes; remain read-only when no such authorization is explicit.
Review only the default output of code2skill-generate. When encountering an advanced-validation format, a legacy version, or an unrecognized directory, explain that this process does not apply instead of forcing the directory through it.
Search only the authorized source roots. When a client or Consumer exists, focus on business invocations actually triggered by the client/Consumer. When no client exists, start from the public API, RPC, Service, message, or task entry point specified by the user. Trace only the code required to prove a representative standard path; do not descend into backend Services, databases, downstream messaging, approvals, or complete business validation.
By default, do not:
- call real business interfaces or write interfaces;
- install, register, or deploy MCP for the review;
- scan the entire machine for unauthorized source code;
- modify the generated package, source code, or tests;
- write temporary goal lists or path derivations into the repository.
What ships with it
2 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.
- 1mo ago First seen · 140 lines · 32 tokens per session scan A b8d25fb4a3f7
code2skill-review-flow is a skill published in the GitHub repository leechen298/Code2Skill (9 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 2,235 once invoked, about $0.0001 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 skills, from other repositories
delivery-proof
Delivery proof and the doublecheck report. Use when the work is done and the delivery must be proven — consolidate the spec, test timeline, review verdicts, and verification checks into a doublecheckreport, and only then claim completion.
red-green-tdd
Red/green test discipline for implementation work. Use once a doublecheck spec is on record and implementation is about to start — write a test that fails for the missing behavior, run it to see it fail (red), make the change, run again to see it pass (green).
codebase-design-zh
A set of design principles for creating modules with small interfaces and substantial behaviour behind them. It explains terms such as interface, implementation, adapter, and seam in plain terms for this design approach.
dev-qa
A development and quality process for building software, testing it, and checking it for security problems. It separates implementation, quality assurance, and security review while coordinating their handoffs.
tdd-zh
A test-first development guide for building features or fixing bugs. Test-driven development, or TDD, means writing a test that fails, making it pass with the smallest change, and then improving the code.
implement-zh
An implementation workflow for completing work described in a specification or tickets. It encourages test-first development where appropriate, runs checks during the work, and ends with review and a commit.