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 ashaykubal/essential-agents-skills --skill subagent-output-templatinggit clone --depth 1 https://github.com/ashaykubal/essential-agents-skillsWrote 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/ashaykubal/essential-agents-skills/subagent-output-templating)<a href="https://agentmods.dev/skills/ashaykubal/essential-agents-skills/subagent-output-templating"><img src="https://agentmods.dev/badge/skills/ashaykubal/essential-agents-skills/subagent-output-templating/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/ashaykubal/essential-agents-skills/subagent-output-templating"><img src="https://agentmods.dev/badge/skills/ashaykubal/essential-agents-skills/subagent-output-templating.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.00050 | $0.02705 |
| Opus 5 | $0.00025 | $0.01352 |
| Sonnet 5 | $0.00010 | $0.00541 |
| Haiku 4.5 | $0.00005 | $0.00270 |
Grade A, and why
subagent-output-templating 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 10d 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
97% identical to subagent-output-templating — 834 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.
How it starts
The opening of the file, as written. The whole thing — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-Agent Output Templating
Overview
This skill provides standardized templates for sub-agent OUTPUT formatting. It complements subagent-prompting (P0.1) which defines INPUT structure:
| Skill | Purpose |
|---|---|
subagent-prompting |
How to prompt sub-agents (GOAL/CONSTRAINTS/CONTEXT/OUTPUT) |
subagent-output-templating |
How sub-agents report results (logs, summaries, diagnostics) |
Use this skill when:
- Defining output requirements for sub-agent invocations
- Parsing sub-agent results in pipeline stages
- Ensuring consistent log formats across all agents
Log File Format
File Location
logs/{agent-name}-{YYYYMMDD-HHMMSS}.yaml
Example: logs/bulwark-code-auditor-20260111-143022.yaml
YAML Schema
# Required: Metadata block
metadata:
agent: {agent-name} # e.g., bulwark-code-auditor
timestamp: {ISO-8601} # e.g., 2026-01-11T14:30:22Z
model: {model-used} # sonnet, haiku, or opus
task_id: {unique-identifier} # For tracking across pipeline stages
duration_ms: {execution-time} # Execution duration in milliseconds
# Required: Goal from the prompt (for traceability)
goal: "{GOAL from 4-part prompt}"
# Required: Completion report
completion:
why:
problem: "{What was broken/missing}"
root_cause: "{Why it happened}"
solution: "{What was implemented}"
what:
- file: {path}
lines: "{range}"
change: "{description}"
trade_offs:
gained:
- "{benefit 1}"
cost:
- "{drawback 1}"
risks:
- risk: "{description}"
mitigation: "{how addressed}"
severity: {low|medium|high|critical}
next_steps:
- "{action item 1}"
# Required for code-writing agents (omit for read-only agents):
# Pipeline suggestions from implementer-quality.sh output
pipeline_suggestions:
- pipeline: "{recommended pipeline name}"
target_files:
- "{file path}"
reason: "{why this pipeline is recommended}"
# Required: Summary for main thread (100-300 tokens)
summary: |
{Concise summary for main thread consumption}
# Required: Diagnostic output
diagnostics:
model_requested: {model}
model_actual: {model}
context_type: {main|forked}
parent_vars_accessible: {true|false}
hooks_fired:
- {hook-name}
execution_time_ms: {duration}
completion_status: {success|error|timeout}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 416 lines · 50 tokens per session scan A 6410caedce1f
subagent-output-templating is a skill published in the GitHub repository ashaykubal/essential-agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 2,705 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to subagent-output-templating, differing in 834 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…