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 rileyhilliard/agentrc --skill preflight-checksgit clone --depth 1 https://github.com/rileyhilliard/agentrcWrote 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/rileyhilliard/agentrc/preflight-checks)<a href="https://agentmods.dev/skills/rileyhilliard/agentrc/preflight-checks"><img src="https://agentmods.dev/badge/skills/rileyhilliard/agentrc/preflight-checks.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.1 | $0.00035 | $0.00830 |
| Opus 5 | $0.00017 | $0.00415 |
| Sonnet 5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
preflight-checks 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 6d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preflight Checks
Run the project's code quality tools before committing. Catch errors early instead of letting pre-commit hooks catch them.
Tool Detection
Detect available tools from project config files. Check in this order:
| Config File | Tool | Check Command | Fix Command |
|---|---|---|---|
package.json scripts |
npm/yarn/pnpm | Look for lint, typecheck, format, check scripts |
Run with --fix where available |
.eslintrc* / eslint.config.* |
ESLint | npx eslint <files> |
npx eslint --fix <files> |
tsconfig.json |
TypeScript | npx tsc --noEmit |
Manual fix required |
.prettierrc* / prettier in package.json |
Prettier | npx prettier --check <files> |
npx prettier --write <files> |
pyproject.toml with [tool.ruff] |
Ruff | ruff check <files> |
ruff check --fix <files> && ruff format <files> |
pyproject.toml with [tool.mypy] / mypy.ini |
mypy | mypy <files> |
Manual fix required |
pyproject.toml with [tool.black] |
Black | black --check <files> |
black <files> |
.flake8 / setup.cfg with [flake8] |
Flake8 | flake8 <files> |
Manual fix required |
go.mod |
Go | go vet ./... |
gofmt -w <files> |
Cargo.toml |
Rust | cargo clippy |
cargo clippy --fix |
.pre-commit-config.yaml |
pre-commit | pre-commit run --files <files> |
Runs auto-fix internally |
Execution Order
Run tools in this order. Each step can change code that later steps check.
- Formatters (auto-fix): prettier, black, ruff format, gofmt
- Linters (auto-fix where possible): eslint --fix, ruff check --fix
- Type checkers (manual fix): tsc, mypy, pyright
Scope
Only check files that are staged or modified. Don't run checks on the entire codebase.
# Staged files
git diff --cached --name-only --diff-filter=ACM
# Unstaged modified files
git diff --name-only --diff-filter=ACM
Filter to relevant extensions for each tool (e.g., only .ts/.tsx for tsc, only .py for ruff).
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.
- 6d ago First seen · 77 lines · 35 tokens per session scan A 4eacf3792299
preflight-checks is a skill published in the GitHub repository rileyhilliard/agentrc (3 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 830 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject and detailed markdown body. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md. Each change type gets its own markdown heading (# emoji + type), with…