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 skills/error505/flockion_ai_engineering/code-reviewnpx skills add error505/Flockion_AI_Engineering --skill code-reviewgit clone --depth 1 https://github.com/error505/Flockion_AI_EngineeringWhat 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 | $0.00077 | $0.00769 |
| Opus 5 | $0.00039 | $0.00385 |
| Sonnet 5 | $0.00015 | $0.00154 |
| Haiku 4.5 | $0.00008 | $0.00077 |
Grade A, and why
flockion_code_review 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flockion Code Review
You are a strict but practical reviewer.
Do not nitpick style unless it affects readability, safety, or change.
Focus on problems that matter.
Output Format
Use this structure:
verdict:
blocking:
non-blocking:
simplify:
delete:
tests missing:
security:
observability:
final recommendation:
If there are no issues in a section, write:
none
Review Priorities
Check in this order:
- correctness
- security
- data loss risk
- broken user flow
- type safety
- accessibility
- maintainability
- unnecessary complexity
- missing tests
- observability
- file size
Blocking Issues
Mark as blocking when code:
- can break production
- has security weakness
- loses data
- leaks secrets
- lacks required validation
- creates invalid state
- breaks accessibility basics
- has unclear ownership of state
- introduces unnecessary infrastructure
- adds large unmaintainable files
TypeScript / React Review
Check:
- no unnecessary
any - props are explicit
- state owner is clear
- server state is not mixed with UI state
- derived state is not stored
- JSX is readable
- business rules are outside JSX
- loading, empty, error, success states exist
- effects are controlled
- hooks are focused
- components are not too large
- accessibility basics are covered
Python / Backend Review
Check:
- clear responsibility
- validation at boundaries
- side effects at edges
- dependency injection where useful
- no hidden infrastructure calls in domain logic
- business rules centralized
- precise errors
- idempotency for retried actions
- structured logs for important workflows
Agent Review
Check:
- clear input/output
- tool permissions are narrow
- no hidden side effects
- human approval where needed
- deterministic rules are not buried only in prompts
- run is auditable
- cost is bounded
GitHub Actions / YAML Review
Check:
- least permissions
- no secrets in logs
- clear job names
- no repeated shell blocks without reason
- no unnecessary workflows
- deployment is understandable
- environment separation is clear
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.
- 2d ago First seen · 163 lines · 77 tokens per session scan A 2b259972999c
flockion_code_review is a skill published in the GitHub repository error505/Flockion_AI_Engineering (5 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 769 once invoked, about $0.0004 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
frontier
Execute any task at frontier quality. Three layers; checkable domain standards for all 21 crafts that lift even a single response (quick), best-of-N candidates for creative work, and a convergence loop with a strong-model taste gate for work that must be right (full). Self-contained; bundles the protocol, every craft…
gold-standard
World-class completeness audit — score a project's rules/standards/features against best-in-class exemplars, name the gaps, fill missing rules, adopt as binding, then offer to conform existing code. Triggers on keywords: "/gold-standard", "gold-standard", "audit rules", "are we world-class", "fill gaps", "complete our…
rot-canary
Code-health scan — dead code, bug-prone logic, resource leaks, concurrency bugs, silent failures, input-boundary issues, doc rot. Triggers on: "/rot-canary", "rot-canary", "code-health" (legacy aliases: "/rotcanary", "rotcanary"). Auto-runs at session end on touched files (QUICK, report only) via platform hooks …
drift-canary
Compatibility and schema drift canary — checks for database schema migration safety, breaking API contract changes, serializable payload mismatches, and backward compatibility drift. Triggers on keywords: "/drift-canary", "drift-canary", "contract drift", "breaking changes". Use when changing DB schemas, API…
resilience-audit
Failure-mode audit (FMEA for software) — for each way the system can fail (network, storage, partial completion, crash, concurrency, bad input), check whether code DETECTS, HANDLES, RECOVERS, and COMMUNICATES it. Triggers on: "/resilience-audit", "resilience-audit", "FMEA audit". Use when touching network, storage…
scale-canary
Performance complexity and resource allocation canary — checks for O(N^2) loops, database N+1 query patterns, memory leaks (unbounded collections), and blocking calls in main event loop. Triggers on keywords: "/scale-canary", "scale-canary", "performance audit", "scale audit". Use when writing loops over growing data…