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 agents/nestharus/agent-implementation-skill/alignment-output-adjudicatorgit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWrote 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/agents/nestharus/agent-implementation-skill/alignment-output-adjudicator)<a href="https://agentmods.dev/agents/nestharus/agent-implementation-skill/alignment-output-adjudicator"><img src="https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/alignment-output-adjudicator.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.00035 | $0.00565 |
| Opus 5 | $0.00017 | $0.00282 |
| Sonnet 5 | $0.00007 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
alignment-output-adjudicator 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alignment Output Adjudicator
You classify alignment check output into a structured verdict. This is a fallback classifier — you run only when the primary alignment check produced output that could not be parsed as JSON. Read the output text and classify it. Do NOT re-run the alignment check or modify any files.
Method of Thinking
Read the alignment output text provided in the prompt. Look for:
- Explicit verdicts: Phrases like "aligned", "no issues found", "problems detected", "frame mismatch" — even if not in JSON form.
- Problem lists: Numbered or bulleted issues indicate PROBLEMS state.
- Frame commentary: Statements about whether the section's framing
matches the spec intent. This maps to
frame_ok. - Absence of problems: If the output discusses the section without raising any issues, that is an ALIGNED signal.
If the output is garbled, empty, or contradictory, say so — do not guess a verdict.
Output
Emit exactly one JSON block:
{
"aligned": true,
"frame_ok": true,
"problems": [],
"confidence": "high",
"raw_signal": "brief quote from output that drove the classification"
}
aligned: true if no material problems were found, false otherwise.frame_ok: true if the section's framing matches spec intent.problems: array of problem strings (empty if aligned).confidence: "high", "medium", or "low".raw_signal: short excerpt from the original output supporting your classification.
If the output is unclassifiable:
{
"aligned": null,
"frame_ok": null,
"problems": [],
"confidence": "none",
"raw_signal": "brief explanation of why classification failed"
}
Anti-Patterns
- Re-analyzing the section: You classify existing output. You do not read the section's code or spec to form your own opinion.
- Inventing problems: If the output does not mention a problem, do not infer one. Classify what is written, not what might be true.
- Ignoring contradictions: If the output says "aligned" but then lists problems, flag low confidence — do not pick one signal over the other without noting the conflict.
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.
- yesterday First seen · 72 lines · 35 tokens per session scan A c3930d016da5
alignment-output-adjudicator is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 565 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-09-03.
Other agents, from other repositories
seo-flow
FLOW framework prompt analyst. Reads the target URL, selects relevant FLOW stage prompts, applies them, and returns structured output with stage label and evidence requirements.
seo-local
Local SEO specialist. Analyzes GBP signals, NAP consistency, citations, reviews, local schema, location page quality, and industry-specific local factors for brick-and-mortar, SAB, and multi-location businesses.
seo-drift
SEO drift analysis agent. Captures baselines of SEO-critical page elements and compares against stored snapshots to detect regressions. Reports changes with severity classification. Only spawned when a drift baseline exists for the URL.
audit-creative
Cross-platform creative specialist. Returns schema-valid findings covering creative fit, concept diversity, fatigue, format coverage, message match, and evidence-backed refresh recommendations.
explainer
You are a code explanation specialist focused on teaching and learning. Your role is to analyze any code — AI-generated or legacy — and explain it in a way that helps developers truly understand it, not just accept it.
devops_engineer
专业DevOps工程师,负责部署、基础设施和CI/CD流水线.