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 aaronnat23/disp8ch --skill output-skillgit clone --depth 1 https://github.com/aaronnat23/disp8chWrote 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/aaronnat23/disp8ch/output-skill)<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/output-skill"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/output-skill.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.00000 | $0.00437 |
| Opus 5 | $0.00000 | $0.00218 |
| Sonnet 5 | $0.00000 | $0.00087 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
output-skill 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 8d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Skill — Full-Output Quality Enforcement
Use this skill when the task requires complete, production-grade code output with no omissions, placeholders, or abbreviated patterns. Prevents partial implementations.
Use when
- Generating complete implementations that will be used directly without further editing.
- The user requests "full code," "complete implementation," or "production-ready" output.
- Code generation tasks where placeholder comments would be unacceptable.
- Any task where "for brevity" shortcuts would leave the output broken.
Core Principle
Treat every task as production-critical. A partial output is a broken output. There is no acceptable middle ground between complete and incomplete code.
Prohibited Output Patterns
// ...rest follows same pattern// TODO: implement/* ... */placeholder blocks// for brevity// similar to above- Skeleton implementations when full code was requested.
- Prose descriptions substituting for actual code.
- Truncated function bodies.
- Incomplete import lists.
Process Workflow
- Identify the total number of deliverables expected (functions, components, files).
- Generate each one completely before moving to the next.
- Cross-check the output against the original request.
- Ensure all imports are present and all referenced variables are defined.
Handling Long Outputs
- When approaching context or token limits, stop at a natural breakpoint (end of function, end of component).
- Insert a pause marker:
<!-- CONTINUE: [description of what comes next] -->. - Do not compress, summarize, or skip any sections.
- On resumption, continue exactly from the pause marker without recapping.
Verification Checklist (apply before responding)
- All requested functions/components are present.
- No placeholder comments remain.
- All imports are included.
- All referenced types and interfaces are defined.
- Error states and edge cases are handled.
- The code runs without modification.
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.
- 8d ago First seen · 49 lines · 0 tokens per session scan A 19fd64d806cb
output-skill is a skill published in the GitHub repository aaronnat23/disp8ch (99 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 437 tokens. 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
create-scraper
Given a careers page URL, uses Playwright browser tools to explore the page, identify reliable scraping patterns (preferring hidden JSON APIs over DOM scraping), then writes a TypeScript Scraper subclass for that company.
find-companies
Uses a public resource to retrieve a list of the current top tech companies, and detects whether they have listings on job boards with public APIs.
verify
How to run and drive this app to verify UI/server changes at runtime.
android-use
Control Android devices via ADB. Use when user asks to tap, swipe, type, launch apps, take screenshots, or automate Android device interactions.
agent-initialization
Initialize an Agent's settings from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.
update-setup
A one-time setup wizard for creating a personalised upgrade guide for a workspace. It checks for an existing guide, identifies the current version and installation clues, and requires confirmation of the installation method before writing a new guide.