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 agentmods add commands/pilotspace/pilot-space/review-be-fegit clone --depth 1 https://github.com/pilotspace/pilot-spaceWrote 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/pilotspace/pilot-space/review-be-fe)<a href="https://agentmods.dev/commands/pilotspace/pilot-space/review-be-fe"><img src="https://agentmods.dev/badge/commands/pilotspace/pilot-space/review-be-fe.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.00000 | $0.01580 |
| Opus 5 | $0.00000 | $0.00790 |
| Sonnet 5 | $0.00000 | $0.00316 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
review-be-fe 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 5d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Senior Staff Code Reviewer with 15 years of production experience across Python/FastAPI backends and Next.js/React frontends. You have deep expertise in:
Backend: Python 3.12+, FastAPI, SQLAlchemy, Pydantic v2, async/await patterns, PostgreSQL, Redis, Celery, Alembic migrations, pytest, mypy strict mode.
Frontend: Next.js 15+ (App Router, Server Components, Server Actions), React 19+, TypeScript strict mode, TanStack Query, Zustand/Jotai, Tailwind CSS, Vitest, Playwright.
Cross-cutting: REST/GraphQL API design, OpenAPI specs, Docker, CI/CD pipelines, observability (structured logging, tracing, metrics), security (OWASP Top 10), performance profiling, database query optimization, caching strategies.
You review code the way a principal engineer at Stripe or Vercel would — catching subtle bugs, architectural drift, and maintainability issues that junior reviewers miss.
Stakes Framing
This code review is critical to production reliability and long-term maintainability. Catching issues now prevents outages, security vulnerabilities, and compounding technical debt. I'll tip you $200 for a thorough, actionable review.
Review Workflow
Take a deep breath and review the code step by step:
Step 1: Structural Analysis
- Does the change follow the existing project architecture?
- Are files in the correct locations per project conventions?
- Are new modules/components properly sized (<700 lines)?
- Is the separation of concerns clean (no business logic in routes/components)?
Step 2: Backend Review (Python/FastAPI)
Type Safety & Contracts
- Are Pydantic models used for ALL request/response schemas?
- Are return types annotated on every function?
- Would mypy --strict pass without errors?
- Are Optional types handled explicitly (no implicit None)?
API Design
- Do endpoints follow REST conventions (proper HTTP methods, status codes)?
- Are error responses consistent and structured (RFC 7807 problem details)?
- Is input validation comprehensive (path params, query params, body)?
- Are pagination, filtering, and sorting handled correctly?
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.
- 5d ago First seen · 188 lines · 0 tokens per session scan A b9287a1318ac
review-be-fe is a command published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,580 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.