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 TheBeardedBearSAS/claude-craft --skill workflow-analysisgit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/workflow-analysis)<a href="https://agentmods.dev/skills/thebeardedbearsas/claude-craft/workflow-analysis"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/workflow-analysis.svg" alt="Measured on agentmods" 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.00017 | $0.00183 |
| Opus 5 | $0.00009 | $0.00092 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
workflow-analysis 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 3d 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.
What it actually says
Workflow d'Analyse Obligatoire
This skill enforces mandatory analysis before any code modification.
See @REFERENCE.md for detailed documentation.
Quick Reference
Before ANY Change
- Understand: Clear objective + acceptance criteria
- Analyze: Read affected files + dependencies
- Document: Files, impacts, risks, approach
- Validate: User approval if medium/high impact
- TDD: Write tests FIRST
Impact Levels
| Impact | Action |
|---|---|
| Low (1 file, < 1h) | Proceed |
| Medium (2-5 files, migration) | Validate with user |
| High (> 5 files, breaking changes) | Detailed plan required |
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.
- 3d ago First seen · 30 lines · 0 tokens per session scan A 882fdfc5e4a4
workflow-analysis is a skill published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 17 tokens to every session and 183 once invoked, about $0.0001 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-03.
Other skills, from other repositories
outside-in-tdd
Use when writing tests from the outside-in, defining behavior before code, or any feature where tests should start from observable business behavior and let internal design emerge.
red-synthesize-green
Use when implementing any feature or fix using TDD, before writing any implementation code.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
principles
Metric literacy for the measures this plugin reports: what cyclomatic complexity, cognitive complexity, Halstead difficulty, lines per file, duplication, coverage, CRAP, and type debt mean, and what none of them can tell you. Four reference files carry the definitions and what each collector really computes, every…
test-driven-development
Implement a feature or bugfix test-first using the red-green-refactor cycle — write a failing test, watch it fail, write the minimal code to pass, then clean up. Works in any language or test runner. Use when building new behaviour or fixing a bug and you want the test to actually prove the code works.
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.