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 plearaj/code-flow-skill --skill code-flow-qagit clone --depth 1 https://github.com/plearaj/code-flow-skillWrote 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/plearaj/code-flow-skill/code-flow-qa)<a href="https://agentmods.dev/skills/plearaj/code-flow-skill/code-flow-qa"><img src="https://agentmods.dev/badge/skills/plearaj/code-flow-skill/code-flow-qa/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/plearaj/code-flow-skill/code-flow-qa"><img src="https://agentmods.dev/badge/skills/plearaj/code-flow-skill/code-flow-qa.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.00050 | $0.03707 |
| Opus 5 | $0.00025 | $0.01853 |
| Sonnet 5 | $0.00010 | $0.00741 |
| Haiku 4.5 | $0.00005 | $0.00371 |
Grade A, and why
code-flow-qa 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.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Flow — QA Walkthrough
A map is a claim about the code: this function calls that one, execution arrives
here from there, this page renders that component. This walks the map this
project has already written under Code_Flows/ and checks the claim against the
code as it is now -- every node, every edge, every documented component and route
-- and reports each flow as passing, drifted, broken or unchecked, naming the
check that decided it.
Static by default, so it runs anywhere the source does and needs nothing
installed. --live additionally starts the application and exercises it through a
browser, which is the only way to catch a page that renders nothing while every
function it needs is still sitting there in the source.
This skill never edits source code, and never fixes what it finds. A QA pass that quietly repaired things would be a QA pass nobody can reproduce.
User Input
The user's request may name the flows to check, and carries the optional --live,
--base-url and --frontend off flags. Step 1 reads them; with none of them
given, every flow in the registry is checked statically.
Instructions
Follow these steps exactly.
1. Read the Arguments
By default this checks every flow in the registry. The request may narrow and deepen that:
- One or more flow names, matched against each registry entry's
slugandtitle, case-insensitively. Only those are checked. A name matching nothing is an error worth stopping for — say which names you did not recognise and list the slugs that exist, because silently checking all fourteen flows when the user asked about one is a report about the wrong thing. --live— after the static walk, actually run the application and exercise it. Off by default. What it does and refuses to do is step 5.--base-url <url>— attach to an application already running there instead of starting one. Implies--live.--frontend off— skip the component and route walk even where the map recorded a frontend. Off by default; use it when the UI is known to be mid-rewrite and its findings would drown the rest.
What ships with it
1 file 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 · 300 lines · 50 tokens per session scan A b0c87cd937ac
code-flow-qa is a skill published in the GitHub repository plearaj/code-flow-skill (1 stars, last pushed 9d ago), licensed Apache-2.0. It adds 50 tokens to every session and 3,707 once invoked, about $0.0003 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-09-05.
Other skills, from other repositories
buildkite-playwright-failures
Analyze Playwright test logs on Buildkite to extract failed-only tests across jobs.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…