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/mracal/vibe-engineering/structured-outputnpx skills add mracal/vibe-engineering --skill structured-outputgit clone --depth 1 https://github.com/mracal/vibe-engineeringWrote 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/mracal/vibe-engineering/structured-output)<a href="https://agentmods.dev/skills/mracal/vibe-engineering/structured-output"><img src="https://agentmods.dev/badge/skills/mracal/vibe-engineering/structured-output.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.00037 | $0.00412 |
| Opus 5 | $0.00018 | $0.00206 |
| Sonnet 5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
vibe-structured-output 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 5d 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.
This is a copy
100% identical to vibe-structured-output — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
vibe-structured-output
Structure aids comprehension. Every analysis should be scannable before it's readable.
When to Use This Skill
- Producing any analysis, report, or recommendation
- When the output will be shared with others
- When multiple stakeholders with different needs will read the output
- When the response would otherwise be a wall of text
When NOT to Use This Skill
- Simple yes/no answers
- Code-only responses
- Casual conversation
- When the user asks for a specific format
The Format
Every structured output has 4 sections:
1. Executive Summary (5-10 lines)
- Type: [Analysis | Report | Recommendation | Audit]
- Confidence: High / Medium / Low
- Key Finding: [One sentence]
- Recommended Actions: [Count]
- Urgency: Immediate / High / Medium / Low
2. Detailed Analysis
Tables, sections, evidence. This is the meat.
- Use tables for comparisons
- Use bullet lists for findings
- Reference specific files/lines
- Include data, not opinions
3. Next Steps
Numbered, actionable items:
- [Action] — [Owner, if known] — [Priority]
- [Action] — [Owner, if known] — [Priority]
4. Metrics (If Applicable)
| Metric | Current | Target | Status |
|---|---|---|---|
| [name] | [value] | [value] | ✓/⚠/✗ |
Anti-Patterns
- Starting with implementation details instead of summary
- Mixing analysis with recommendations
- Opinions without evidence
- Actions without owners or priorities
- Metrics without targets
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.
- 5d ago First seen · 60 lines · 37 tokens per session scan A 4b7b914ded66
vibe-structured-output is a skill published in the GitHub repository mracal/vibe-engineering (3 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 412 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to vibe-structured-output, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
unity-ui-art-and-motion-production
Use when new or revised Unity UI visuals, icons, panels, 9-slice sprites, component states, HUD or menu layouts, popup motion, screen transitions, or flattened UI screenshot decomposition must be produced through Figma and integrated into uGUI, NGUI, or UI Toolkit; not for UI debugging, localization-only work…
game-screenshot-showcase-and-store-packaging
Use when a Unity team needs approved PlayMode screenshots, immutable capture evidence, reviewed showcase slides, or report-only store screenshot packaging without auto-upload, signing, or submission.
studio-project-scaffold
Use when running gamestudio init, status, or uninit, or bootstrapping a new or adopted game repository with AGENTS.md, HANDOFF.md, .agents/CONTRACT.md, project governance, a subsystem registry, or a per-project adapter report, plan digest, named reviewer, backup root, generated agent overlay, apply, uninstall, and…
using-game-studio-skills
Use when starting any GameStudio-CodexKIT task or when a model runner is unavailable and someone requests a confidence-based PASS.
animation-rigging-import-audit
Use when character animation needs an audit across skeleton, rig, skin weights, avatar, retargeting, clips, events, root motion, compression, import settings, runtime blending, and platform budgets; not for general art preflight.