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.
git clone --depth 1 https://github.com/eugenelim/agent-ready-repoWrote 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/commands/eugenelim/agent-ready-repo/conventions-check)<a href="https://agentmods.dev/commands/eugenelim/agent-ready-repo/conventions-check"><img src="https://agentmods.dev/badge/commands/eugenelim/agent-ready-repo/conventions-check/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/commands/eugenelim/agent-ready-repo/conventions-check"><img src="https://agentmods.dev/badge/commands/eugenelim/agent-ready-repo/conventions-check.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.00028 | $0.00594 |
| Opus 5 | $0.00014 | $0.00297 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
conventions-check 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 10d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify the conventions below and report findings. If your project ships linters that cover any of these, run them; otherwise inspect the files directly and report each check by hand. Don't auto-fix — report findings and let the user decide.
AGENTS.md hygiene
- Root
AGENTS.mdis under 120 lines; a core seed is under 100 lines. CLAUDE.mdis a symlink toAGENTS.md, or a byte-identical copy of it. (Native Windows checkouts can't materialise symlinks without elevation, so an identical regular file is accepted; a diverged regular file is not.)- Scoped or local instruction files are under 80 lines;
_exampleskeletons are under 35. - Internal links resolve.
docs/CHARTER.mdand the Diátaxis guide subdirectories exist.
Agent-artifact hygiene (skills, subagents, commands)
- Every skill, subagent, and command has well-formed YAML frontmatter with
the required keys (
name,description). - Skill directory names match the frontmatter
name; subagent and command filenames match theirname; all kebab-case. - Frontmatter carries no unknown keys.
- Each skill dir contains a
SKILL.mdand no stray.mdsiblings. - Internal markdown links inside each artifact resolve.
Credentialed-skill rules
Scoped to skills whose SKILL.md declares metadata.credentialed: true
(project-specific fields live under metadata: per the agentskills.io spec):
- The body contains a
### Security rules (non-negotiable)heading and the three required security substrings inside that section (the verbatim "Don't" block). - For
metadata.primitive-class: credentialed-cli: no script under the skill'sscripts/directory accepts anargparseflag whose normalised name (strip leading-, casefold,-→_) is one of{token, api_token, api_key, bearer, pat, password}. This covers literal strings and"--" + "name"-style concatenation. - No script under a credentialed skill's
scripts/directory contains the substring.agentbundle/credentials.envunless the opt-out comment# credentialed-primitive: reads-creds-directlyappears on the same line.
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.
- 10d ago First seen · 49 lines · 28 tokens per session scan A 7455d6ae51bc
conventions-check is a command published in the GitHub repository eugenelim/agent-ready-repo (20 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 594 once invoked, about $0.0001 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 commands, from other repositories
verify
PitWay: Run approved command checks, or record a manual/review result.
quality-gate
Pre-commit quality check — catches defects the review would flag, so the builder can fix them before committing.
review-pr-staging
Staging review mode — comprehensive review of staging branch before deploy to main.
brief-refresh
Audit docs for staleness and contradictions, propose new features.
review-pr
Context-aware PR review — analyzes what the PR touches, spawns domain-specific agents with project conventions. Supports staging reviews.
ms-review
description: PitWay: Role-based milestone review workflow (start/brief/record/report/decide) argument-hint.