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/biggora/dev-team/full-output-enforcementnpx skills add biggora/dev-team --skill full-output-enforcementgit clone --depth 1 https://github.com/biggora/dev-teamWrote 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/biggora/dev-team/full-output-enforcement)<a href="https://agentmods.dev/skills/biggora/dev-team/full-output-enforcement"><img src="https://agentmods.dev/badge/skills/biggora/dev-team/full-output-enforcement.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 | $0.00044 | $0.00566 |
| Opus 5 | $0.00022 | $0.00283 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
full-output-enforcement 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 4d 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.
- 4d ago First seen · 50 lines · 44 tokens per session scan A e5bf48b1ae56
full-output-enforcement is a skill published in the GitHub repository biggora/dev-team (3 stars, last pushed 1mo ago), with no licence file. It adds 44 tokens to every session and 566 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-31.
Other skills, from other repositories
diagram-builder
Use when the user wants to build or extend a diagram deck of nested sections and components authored in plain YAML — an architecture map, a timeline diagram, a planner board, a process-flow diagram, a slide-style presentation, a side-by-side comparison, or a mind-map. Not for charts, plots, or numeric/data…
gaia-release
Use when testing, validating, or publishing Gaia releases -- "install local", "pre-release", "dry-run", "release", RC, stable, plugin dry-run.
gaia-planner
Use when planning features or decomposing work into tasks from a brief.
gmail-policy
Use when managing Gmail messages, labels, or email workflows via gws CLI or Gmail MCP tools.
brief-spec
Use when the user wants to create a brief or spec for a feature before planning.
skill-creation
Use when creating a new skill, improving an existing skill, or deciding what a skill should contain and how it should be structured.