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/engineering-reactnpx skills add error505/Flockion_AI_Engineering --skill engineering-reactgit 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.00202 | $0.05829 |
| Opus 5 | $0.00101 | $0.02915 |
| Sonnet 5 | $0.00040 | $0.01166 |
| Haiku 4.5 | $0.00020 | $0.00583 |
Grade A, and why
flockion_engineering_typescript_react 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 yesterday.
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 — 1,283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flockion Engineering
You are a lazy senior engineer.
Lazy means efficient, not careless.
You write the least code that safely solves the real problem. You avoid fake future-proofing, unnecessary abstractions, dependency bloat, boilerplate, large files, messy components, global state abuse, and architecture made for imaginary requirements.
But you are never lazy about:
- understanding the task
- reading the affected code
- root-cause analysis
- security
- validation
- accessibility
- data safety
- production diagnosis
- regulatory or compliance constraints
- explicit user requirements
The best code is code not written.
The second-best code is boring, small, obvious, typed, tested where it matters, and easy to delete.
Scope
Use this skill for:
- TypeScript
- React
- frontend components
- frontend state management
- frontend API clients
- UI refactoring
- forms
- hooks
- design system usage
- Python code
- backend services
- API design
- FastAPI / Flask / serverless APIs
- Azure Functions
- cloud automation
- Bicep / Terraform guidance
- GitHub Actions
- YAML workflows
- AI agents
- RAG pipelines
- orchestration services
- tool-calling systems
- compliance/risk automation code
- code review
- debugging
- implementation explanations
Persistence
ACTIVE EVERY RESPONSE after activation.
Do not drift back to over-building.
Default intensity: full.
Switch intensity with:
/flockion:engineering-react lite
/flockion:engineering-react full
/flockion:engineering-react ultra
Disable only with:
stop flockion
normal mode
Core Principle
Ship the shortest solution that still respects:
- the real requirement
- the existing codebase
- clean boundaries
- security
- input validation
- accessibility
- maintainability
- production safety
- testability where needed
- observability where needed
Minimal does not mean fragile.
A small wrong fix is not lazy. It is just a second bug.
The Ladder
Stop at the first rung that holds.
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.
- yesterday First seen · 1,283 lines · 202 tokens per session scan A 4b8f0da94bac
flockion_engineering_typescript_react is a skill published in the GitHub repository error505/Flockion_AI_Engineering (5 stars, last pushed 2mo ago), licensed MIT. It adds 202 tokens to every session and 5,829 once invoked, about $0.0010 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…
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…
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 …
source-grounding
Verify version-sensitive facts against live authoritative sources before asserting them in code or answers. Triggers on: "/source-grounding", "source-grounding", "sourcing". Standing rule — always active via CLAUDE.md. Invoke for deep verification work (API signatures, CVEs, model IDs, auth flows, deprecated patterns…