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 Fearvox/multica-ultimate-workbench --skill workbench-capy-git-dialogue-guardrailsgit clone --depth 1 https://github.com/Fearvox/multica-ultimate-workbenchWrote 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/fearvox/multica-ultimate-workbench/workbench-capy-git-dialogue-guardrails)<a href="https://agentmods.dev/skills/fearvox/multica-ultimate-workbench/workbench-capy-git-dialogue-guardrails"><img src="https://agentmods.dev/badge/skills/fearvox/multica-ultimate-workbench/workbench-capy-git-dialogue-guardrails/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/fearvox/multica-ultimate-workbench/workbench-capy-git-dialogue-guardrails"><img src="https://agentmods.dev/badge/skills/fearvox/multica-ultimate-workbench/workbench-capy-git-dialogue-guardrails.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.00040 | $0.00682 |
| Opus 5 | $0.00020 | $0.00341 |
| Sonnet 5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
workbench-capy-git-dialogue-guardrails 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 12d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 12d ago First seen · 82 lines · 40 tokens per session scan A 09ec29635114
workbench-capy-git-dialogue-guardrails is a skill published in the GitHub repository Fearvox/multica-ultimate-workbench (27 stars, last pushed 3mo ago), with no licence file. It adds 40 tokens to every session and 682 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
dx-roaster
Brutally honest developer-experience audit for a GitHub repo. Scores 10 DX dimensions (time-to-first-success, README clarity, visual proof, install, quick-start, docs, examples, community, trust, marketing), writes a shareable roast in the requested tone (brutal/honest/kind), produces a prioritized action plan ranked…
hermes-change-review
Use when a branch, pull request, Kanban task, or implementation must be reviewed separately for intent fidelity, repository quality, and verification evidence before completion or merge is accepted.
stage-refactor-checklist
Comprehensive checklist for refactoring a schemacompiler stage folder. Use EVERY TIME you refactor a compiler stage (resolve, unify, codegen, etc.). Read this before writing any code.
invariant-first-coding
Reason from proven invariants before coding. Use when reviewing fallback logic, narrowing types, handling conversions, deciding whether an error path is real or impossible, removing overdefensive code, or when the user questions whether code is being too theatrical, too hedged, or not fail-closed enough.
torvalds
Design engineering principles for removing special cases. Use when designing new systems, extracting shared packages, refactoring conditional logic, deciding whether to add a flag or change the interface, or when the user invokes "good taste" or asks for a cleaner algorithm.
code-review
Staff engineer code review. Adapted from GStack's /review (Garry Tan, github.com/garrytan/gstack) for Cursor. Finds bugs that pass CI but blow up in production. Auto-fixes the obvious ones. Flags completeness gaps.