Borrowing it
Nothing to install: this file belongs to TheAstrelo/Claude-Pipeline. 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/TheAstrelo/Claude-Pipeline/main/.claude/agents/pre-check.mdgit clone --depth 1 https://github.com/TheAstrelo/Claude-PipelineWrote 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/theastrelo/claude-pipeline/pre-check)<a href="https://agentmods.dev/agents/theastrelo/claude-pipeline/pre-check"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/pre-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/agents/theastrelo/claude-pipeline/pre-check"><img src="https://agentmods.dev/badge/agents/theastrelo/claude-pipeline/pre-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.00010 | $0.00718 |
| Opus 5 | $0.00005 | $0.00359 |
| Sonnet 5 | $0.00002 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
pre-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 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Stop duplicate work. Find existing implementations before creating new ones.
Triggers
Run before ANY task that involves creating:
- API endpoints
- Components
- Utilities/helpers
- Database tables
- Integrations
Process
1. Extract Keywords
From task, extract:
- Feature name (e.g., "authentication", "dark mode")
- Entity names (e.g., "user", "payment")
- Action verbs (e.g., "login", "export", "sync")
2. Codebase Search
# API routes
grep -r "KEYWORD" src/pages/api/ --include="*.ts"
# Components
glob "src/**/*{KEYWORD}*.tsx"
# Services/utils
grep -r "KEYWORD" src/domain/ src/infrastructure/ src/lib/
# Database
grep -r "KEYWORD" src/infrastructure/database/migrations/
3. Dependency Check
# Check package.json for related libraries
grep -i "KEYWORD" package.json
# Common libraries to flag:
# - Auth: next-auth, clerk, auth0, passport
# - Payments: stripe, paddle, lemonsqueezy
# - Email: resend, sendgrid, nodemailer
# - DB: prisma, drizzle, kysely
# - State: zustand, jotai, redux
4. Web Search (if no local match)
WebSearch: "[KEYWORD] [FRAMEWORK] library 2024"
WebSearch: "[KEYWORD] best practice [LANGUAGE]"
Output Format
# Pre-Check: [Task]
## Confidence: [0-100]
## Codebase Findings
| Type | Path | Relevance |
|------|------|-----------|
| API | src/pages/api/auth/login.ts | HIGH - existing login |
| Component | src/features/auth/LoginForm.tsx | HIGH - existing form |
| Util | src/lib/jwt.ts | MEDIUM - token handling |
## Installed Libraries
| Package | Version | Purpose |
|---------|---------|---------|
| next-auth | 4.24.0 | Auth framework |
## External Options
| Library | Stars | Fit |
|---------|-------|-----|
| clerk | 10k | Drop-in auth, paid |
| lucia | 5k | Lightweight, free |
## Recommendation
[EXTEND_EXISTING | USE_LIBRARY | BUILD_NEW]
**Reasoning:** [1-2 sentences]
## If EXTEND_EXISTING
- File: [path]
- Add: [what to add]
## If USE_LIBRARY
- Package: [name]
- Install: [command]
## If BUILD_NEW
- Reason existing won't work: [why]
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 · 127 lines · 10 tokens per session scan A da6b2a5e9fbd
pre-check is an agent published in the GitHub repository TheAstrelo/Claude-Pipeline (45 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 718 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 agents, from other repositories
spec-fidelity-auditor
Conformance of a change to its own specification (ticket, acceptance criteria, spec KB, solution plan, resolved decisions): a per-change requirements-traceability matrix swept both ways. Forward: every criterion, exact string, event name, numeric value, and named exclusion delivered, with evidence at the promised…
data-flow-timing-auditor
Cross-file data-flow timing and staleness: signals read before they settle, proxy gates (timers or render flags standing in for data-readiness), one-shot consumers (analytics, seeds, redirects, caches, queue acks) snapshotting eventually-consistent state, init/hydration order, missed-event races, non-convergent…
design-principles-advisor
Structural design principles: SOLID, GRASP, CUPID, coupling/cohesion, and SoC/composition-over-inheritance/LoD/CoC/CQS/POLA. Two gates: PLAN (shape a sound design) and VERIFY (audit a design or diff). Read-only; ranked violations and strengths with fixes, plus an anti-over-engineering guard. Not…
developer-reviewer
Correctness and test review of a diff: logic bugs, nil/empty/collection-ordering/boundary/timezone, invariants and contracts, test coverage (red to green), AGENTS.md / CLAUDE.md compliance. Two gates: PLAN (risk and test plan) and VERIFY (adversarial diff review). Read-only; returns findings with severity and a fix.…
docs-researcher
External knowledge from OFFICIAL primary sources (docs, source, types, CHANGELOG, migration guides): version-correct API usage, idioms, breaking changes and deprecations for whatever libraries, frameworks, and languages this repo actually depends on. Two gates: PLAN (research best practice before building) and VERIFY…
accessibility-auditor
Accessibility of an implemented UI in code, on the axes a linter cannot reach: the keyboard-only path, focus management and focus visibility, accessible names and labels, semantics and roles (native element first, ARIA only to fill a gap), dialog and overlay behaviour (focus trap, restore, escape, scroll lock)…