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 WenyuChiou/agent-collab-skills --skill agent-output-reconcilergit clone --depth 1 https://github.com/WenyuChiou/agent-collab-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/wenyuchiou/agent-collab-skills/agent-output-reconciler)<a href="https://agentmods.dev/skills/wenyuchiou/agent-collab-skills/agent-output-reconciler"><img src="https://agentmods.dev/badge/skills/wenyuchiou/agent-collab-skills/agent-output-reconciler/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/wenyuchiou/agent-collab-skills/agent-output-reconciler"><img src="https://agentmods.dev/badge/skills/wenyuchiou/agent-collab-skills/agent-output-reconciler.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00710 |
| Opus 5 | $0.00015 | $0.00355 |
| Sonnet 5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
agent-output-reconciler 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 7d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-output-reconciler
Reconcile completed task results into one evidence-based report. This skill describes what happened and what conflicts remain. It does not accept work, merge changes, retry tasks, or write canonical memory.
Inputs
- the current plan and its task IDs, roles, scopes, dependencies, and success criteria;
- each task packet, result summary, structured result, and raw-log path;
- the relevant
TaskCheckpointand latestPolicyDecision; - repository diff and test evidence.
Current plans use provider-neutral roles: primary-agent,
delegated-executor, reviewer, and synthesizer. Historical provider fields
may be parsed for migration only and must not influence current routing.
Workflow
- Validate the plan and checkpoint. If either is unreadable, stop and report a blocker. Do not infer missing policy values.
- Inventory every planned task. Preserve
null, missing, cancelled, declined, degraded, and failed results as distinct states. - Filter unusable payloads before synthesis, while retaining a record of what
was filtered and why. Never turn a completed prose result into
nullmerely because an optional structured-output step failed. - Compare actual changed files with each task's declared scope. Record justified transitive changes separately from unexplained drift.
- Verify claimed tests and artifacts from their evidence references. A result without evidence remains unverified even if its prose says "success".
- Identify file collisions, incompatible assumptions, contradictory findings, dependency-order violations, and unresolved risks.
- Compose a reconciliation report using
references/reconciliation_template.md. - Hand the report to
agent-acceptance-gate. Do not convert a reconciliation recommendation into an acceptance decision.
Output contract
The report must contain:
- plan and policy references;
- per-task role, status, evidence references, files changed, tests, and risks;
- filtered or missing result records;
- agreement that is supported by shared evidence;
- contradictions and file conflicts;
- recommended next action with explicit blockers.
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.
- 7d ago Changed · +2 lines 86c47ee4a369
- 9d ago Changed · -326 lines · -13 tokens per session 74d16eca9e27
- 12d ago First seen · 402 lines · 44 tokens per session scan A 7783ab5fa557
agent-output-reconciler is a skill published in the GitHub repository WenyuChiou/agent-collab-skills (26 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 710 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
review-work
Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
one-way-door
Flags irreversible decisions before commit. Use for data models, infra, auth boundaries, API contracts, event schemas, CI/CD.
map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to "map…
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…