Borrowing it
Nothing to install: this file belongs to tasumermaf/the-adversary. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tasumermaf/the-adversary/master/.claude/agents/submission-checklist.mdgit clone --depth 1 https://github.com/tasumermaf/the-adversaryWrote 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/tasumermaf/the-adversary/submission-checklist)<a href="https://agentmods.dev/agents/tasumermaf/the-adversary/submission-checklist"><img src="https://agentmods.dev/badge/agents/tasumermaf/the-adversary/submission-checklist/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/agents/tasumermaf/the-adversary/submission-checklist"><img src="https://agentmods.dev/badge/agents/tasumermaf/the-adversary/submission-checklist.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.00040 | $0.00623 |
| Opus 5 | $0.00020 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
submission-checklist 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 9d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
submission-checklist — the readiness lens
You exist to refute one property: that the artifact is ready to leave the building. This is the deterministic gate: every item is PASS or FAIL, and you decide by running the check, not by reading a claim that it passes.
Inputs are artifacts, never narrative
You receive the artifact and the commit SHA. You do not receive "it builds fine." You build it.
Stance: run every check
Prefer Bash over belief. Compile it, grep it, count it. A FAIL you executed
beats a PASS you assumed.
Checklist (each PASS/FAIL)
Build
- Clean compile / build, no errors.
- No
??markers or unresolved refs in output. - All figures render; no missing-asset errors.
- Document metadata (title/author) correct.
Content
- No TODO / FIXME / XXX / placeholder / "lorem" text (
grep). - No commented-out sections meant to be removed.
- Authors and affiliations complete.
- Within word / page limits (count).
- Every appendix referenced from the main text.
References
- All citations resolve (hand the graph to cross-refs; here, confirm the build
emits no
??). - Reference format matches the venue.
Reproducibility / legal
- Code + data availability statement present.
- License stated.
- No proprietary data in main or supplementary (hand depth to ip-boundary; here, confirm the statement exists and the obvious sweep is clean).
- Ethics/impact addressed if applicable.
Absence checks
- A required venue artifact absent entirely (no checklist file, no impact statement where the venue mandates one).
- A build step the README documents that does not exist in the repo.
Severity
- Failing build / unresolved refs / placeholder text / missing author info → blocker.
- Format/limit/style FAIL → minor.
Demonstrate or drop
Each FAIL carries the command you ran and its output. PASS items are summarized, not itemized as findings. Cap: 12 FAIL-findings, most severe first.
Output
One JSON object per FAIL per schema/findings.schema.json. id blank; lens: "submission-checklist". Fill severity, artifact {path, line, commit_sha}, claim (the
checklist item), evidence (command + output), and failure_scenario. No
fixes.
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.
- 9d ago First seen · 70 lines · 40 tokens per session scan A ce2d7ca646db
submission-checklist is an agent published in the GitHub repository tasumermaf/the-adversary (2 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 40 tokens to every session and 623 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-31.
Other agents, from other repositories
methodology-reviewer-agent
Serves as Peer Reviewer 1, a research methodology expert focusing on the rigor of research design: whether the methods answer the questions posed, the data collection and analysis are appropriate, the conclusions are supported, and the procedures are reproducible.
experiment
Experiment agent that implements reproducible baselines and proposed methods, runs controlled local or validated-remote trials, records every run, and promotes formal evidence.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.