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 agentmods add skills/fluxonlab/skillry/40-agent-workflow-designnpx skills add FluxonLab/Skillry --skill 40-agent-workflow-designgit clone --depth 1 https://github.com/FluxonLab/SkillryWrote 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/fluxonlab/skillry/40-agent-workflow-design)<a href="https://agentmods.dev/skills/fluxonlab/skillry/40-agent-workflow-design"><img src="https://agentmods.dev/badge/skills/fluxonlab/skillry/40-agent-workflow-design.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.00027 | $0.02487 |
| Opus 5 | $0.00014 | $0.01243 |
| Sonnet 5 | $0.00005 | $0.00497 |
| Haiku 4.5 | $0.00003 | $0.00249 |
Grade A, and why
agent-workflow-design 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 2d 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 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.
- 2d ago First seen · 157 lines · 27 tokens per session scan A 5d49f64af7b7
agent-workflow-design is a skill published in the GitHub repository FluxonLab/Skillry (2 stars, last pushed 8d ago), with no licence file. It adds 27 tokens to every session and 2,487 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
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
gerador-soul
Gera um arquivo SOUL.md completo e estruturado para qualquer agente ou assistente de IA. Use esta skill SEMPRE que a pessoa usuária quiser criar um SOUL.md, definir a identidade de um agente, descrever a "alma" de um assistente, ou usar os gatilhos "/soul", "/soul.md" ou "gerar soul". Ative também quando a pessoa…
craque-neto
Faz análise de risco de projetos gritando a real, sem bajulação, no tom de voz do ex-jogador José Ferreira Neto, o 'Craque Neto', apresentador do 'Donos da Bola' (Band) e da 'Rádio Craque Neto'. A resposta é só a bronca do Neto: texto corrido de até 200 palavras, primeira pessoa, linguagem do povo, palavrão pesado…
spec
Create a spec (PRD) through user interview, codebase exploration, and module design. Use when starting a feature with unclear requirements, when the user asks to spec or define what to build, or says "write a spec" or "write a PRD". Don't use when requirements are crisp and a plan already exists (use /plan or /build).
triage-review
Fetch unresolved review comments on a GitHub PR (Copilot bot + human reviewers), verify each against the current code, and classify as Address / Skip / Optional / Discuss with a one-line rationale. Use when the user asks which review comments to address, to triage Copilot/reviewer feedback, sort signal from noise on a…
visual-review
Render a GitHub Pull Request diff as a self-contained HTML page where each changed hunk is annotated with a software-principle explanation and a suggested simplification. Use when the user wants to review a PR visually, generate an HTML/visual diff report, or see PR feedback linked to principles (e.g. an unnecessary…