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 boshu2/agentops --skill anti-ceremonygit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/anti-ceremony)<a href="https://agentmods.dev/skills/boshu2/agentops/anti-ceremony"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/anti-ceremony/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/boshu2/agentops/anti-ceremony"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/anti-ceremony.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.00033 | $0.00793 |
| Opus 5 | $0.00016 | $0.00396 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
anti-ceremony 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 today.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-Ceremony
Keep work tied to the caller-visible outcome and the proof still needed for it. The default guard is a single, artifact-free judgment before RPI Plan; the full honesty audit runs only on an explicit "full anti-ceremony audit" request.
Prompt
Quick guard. Outcome: "ao gate check lists the probe-coverage row". Proposed
process work: a coverage dashboard and a second audit pass. Remaining proof:
the gate row, green in CI. Stop condition: that gate passes on main.
It's working if
- The response is the YAML shape below and nothing else: no file appears
under
.agents/, and no tracker write is issued. reason:is one sentence, andparked_process_work:names the dashboard-shaped items.- A full audit appears only after the caller wrote
full anti-ceremony audit.
Quick guard
- Freeze the caller-visible outcome in one short statement.
- Park proposed process work that has no concrete consumer, gated subject or release decision, observed defect, or retirement condition.
- Name the implementation or independent proof still missing.
- Name the condition that ends this traversal.
- Return
STOPwhen the traversal would only create control artifacts or the frozen outcome is already sufficiently proved; otherwise returnCONTINUE.
Progress needs evidence tied to acceptance or a named blocking uncertainty.
Digest movement, finding counts, and additional reviews alone earn no credit.
Informative red can justify a different experiment inside an explicitly selected
outer goal's unchanged acceptance and allowance; repeated no-information work
cannot. Keep required independent proof in remaining_proof, including every
necessary unresolved finding. Apply Validate's effect-based risk rule to the
cost of proof; never weaken the exact-subject or all-acceptance PASS bar.
Perform the guard exactly once in memory. Parking is a field in the response, not a tracker or delivery mutation. Return this shape:
decision: CONTINUE | STOP
reason: <exactly one sentence>
frozen_outcome: <nonempty string>
parked_process_work: [<work item>, ...]
remaining_proof: [<proof item>, ...]
stop_condition: <nonempty string>
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.
- today Changed · +8 lines 9588de86304a
- 5d ago Changed · +3 lines f5ba0a5f7703
- 9d ago First seen · 84 lines · 33 tokens per session scan A c10d2b26d8ea
anti-ceremony is a skill published in the GitHub repository boshu2/agentops (433 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 793 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
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
commit-push-pr
Use when asked to commit, push a feature branch, and open or update a pull request with gh in one pass. Not for a push with no PR: use commit-push. Not for a PR body alone: use create-pull-request.
commit
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
duet
Use when the user invokes /duet, says "pair with me", or faces aesthetic, architectural, or irreversible decisions.