audit-post

audit-post is a skill for Claude Code, Codex from DanceNitra/agora. It costs 0 tokens per session (2,917 once invoked), scanned A, original, MIT.

A required procedure for checking one already-published scientific post, correcting problems, and checking the corrected version again before committing it.

In plain words
What is it for?
Use it to audit scientific posts, verify their reasoning and sources, apply fixes, re-audit them, and then commit the result.
Why use it?
It reduces the chance that unsupported claims, incorrect citations, or other review failures remain in published work.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/dancenitra/agora/audit-post
Any agent
npx skills add DanceNitra/agora --skill audit-post
Clone the repo
git clone --depth 1 https://github.com/DanceNitra/agora

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for audit-post

README.md
[![agentmods](https://agentmods.dev/badge/skills/dancenitra/agora/audit-post.svg)](https://agentmods.dev/skills/dancenitra/agora/audit-post)
Your own site
<a href="https://agentmods.dev/skills/dancenitra/agora/audit-post"><img src="https://agentmods.dev/badge/skills/dancenitra/agora/audit-post.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,917 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02917
Opus 5 $0.00000 $0.01458
Sonnet 5 $0.00000 $0.00583
Haiku 4.5 $0.00000 $0.00292

Measured 5d ago against content hash f55f0480515d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

audit-post 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.

.claude/skills/audit-post/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Audit-Post — the ONE correct, unskippable procedure for auditing a published post

What this is

The end-to-end procedure for auditing one already-published post to a scientific-organization standard. It chains the adversarial skills and — critically — re-runs the auditor on the CORRECTED post to confirm it now passes clean before committing. We are a scientific organization; we do not ship missteps. Run EVERY step, in order, for EVERY post. No light/inline version. Fewer posts done FULLY > more done shallow.

Defined 2026-06-29 after the owner caught two failures: (1) shortening the audit to a single citation verifier + inline reasoning (missed a "Bayesian" mislabel, a strawman baseline, a wrong-estimand, and a "textbook dressed as our law" overclaim across posts #7–#10); (2) dropping the re-audit-after-fix step — I fixed and committed WITHOUT re-running the auditor on the corrected post to confirm the fix is clean.

Updated 2026-07-01 after a THIRD failure: audits #16–#19 all ran stress-claim + verify-claims but never ran storm-research at all, because this file — written 2026-06-29 — predates the owner's 2026-07-01 PERMANENT standing gate ("VALIDATE → STORM → AUDIT → VERIFY, storm is dominant, never skip, applies to everything not just flagship posts"). The gate overrides every skill file by design, but relying on remembering an overriding rule from a different document is exactly the failure mode that gate exists to prevent. STORM is now Step 3 below, hard-coded into the numbered procedure itself — not something to recall from memory. If a future owner rule changes the required order again, update this file itself, don't leave the gap for the model to bridge silently.

Updated again 2026-07-01, SAME DAY after a FOURTH failure, caught within an hour of the third: the "run the /seo Mode-A check" instruction was a clause buried inside a bigger step (old step 6, mixed in with bilingual-fix instructions), and in practice it was never actually executed as a distinct checklist pass on audit #19 — I made ad-hoc meta/JSON-LD/internal-link edits without running the LLM-summary self-test, without checking the Three Kings against the char-length rules, and without requesting re-indexing. Writing a step into a paragraph is not the same as writing it as a step. SEO validation is now its own numbered step (7), with the specific /seo Mode-A checklist items spelled out inline so there's no clause to skim past. Pattern to notice going forward: if a "run X" instruction is a sub-clause of a different step instead of its own step, that's the shape of thing that gets silently skipped — split it out.

Read the full file on GitHub · 151 lines

Changes

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.

  1. 5d ago First seen · 151 lines · 0 tokens per session scan A f55f0480515d

Subscribe to this mod's changes

audit-post is a skill published in the GitHub repository DanceNitra/agora (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,917 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-31.