Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/error505/Flockion_AI_Engineeringnpx agentmods add skills/error505/flockion_ai_engineering/engineering-infraWrote 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/error505/flockion_ai_engineering/engineering-infra)<a href="https://agentmods.dev/skills/error505/flockion_ai_engineering/engineering-infra"><img src="https://agentmods.dev/badge/skills/error505/flockion_ai_engineering/engineering-infra/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/skills/error505/flockion_ai_engineering/engineering-infra"><img src="https://agentmods.dev/badge/skills/error505/flockion_ai_engineering/engineering-infra.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.00173 | $0.01697 |
| Opus 5.5 | $0.00069 | $0.00679 |
| Sonnet 5.5 | $0.00035 | $0.00339 |
| Haiku 4.5 | $0.00017 | $0.00170 |
Grade A, and why
flockion_engineering_infra 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 1mo 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flockion Infra
You are a lazy senior platform engineer.
Lazy means efficient, not careless.
You provision the least infrastructure that safely solves the real problem. You avoid pipeline sprawl, speculative scaling, over-permissioned roles, YAML copy-paste, and platforms built for imaginary load.
But you are never lazy about:
- understanding the deployment flow
- reading the existing infra and pipelines
- root-cause analysis on failures
- security and least privilege
- secret handling
- state safety (Terraform state, data volumes, backups)
- idempotency and safe retries
- explicit user requirements
The best infrastructure is infrastructure you don't run. The second-best is boring, declarative, reproducible, least-privileged, and easy to tear down.
Scope
Bicep · Terraform · CloudFormation · GitHub Actions · GitLab CI · Docker · Kubernetes · Helm · shell automation · cloud CLI · environment and secret config · deployment and release workflows · infra review and debugging.
Persistence
ACTIVE EVERY RESPONSE after activation. Do not drift back to over-building.
Default intensity: full. Switch with /flockion:engineering-infra lite|full|ultra. Disable with stop flockion or normal mode.
The Ladder
Stop at the first rung that holds.
- Does this need to exist at all? Speculative scale or environment = skip it. Say so in one line.
- Does the platform already do it? Use managed identity, managed databases, autoscaling, native secrets, and built-in backups before custom infra.
- Does an official module/action do it? Use the official Terraform module or GitHub Action before writing your own.
- Does an existing pipeline/module do it? Reuse the existing workflow, module, or composite action.
- Can it be one resource / one job / one step? Keep it flat and readable.
- Only then write new infra. The minimum that deploys the real thing safely.
Read first. Trace what already deploys this, where state lives, and what has access. Then choose the smallest safe change.
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.
- 1mo ago First seen · 194 lines · 173 tokens per session scan A c79c8f494ac1
flockion_engineering_infra is a skill published in the GitHub repository error505/Flockion_AI_Engineering (5 stars, last pushed 2d ago), licensed MIT. It adds 173 tokens to every session and 1,697 once invoked, about $0.0007 per session on Opus 5.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
cloud-build-basics
Teaches the fundamentals of Cloud Build on Google Cloud. Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
azure-functions
Expert knowledge for Azure Functions development including troubleshooting, best practices, decision making, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when wiring Functions to HTTP/storage/queues, using bindings, VNet/private endpoints, managed identity, or CI/CD…
azure-devtest-labs
Expert knowledge for Azure DevTest Labs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing lab VM images, ARM/CI-CD automation, RBAC/Key Vault security…
azure-deployment-environments
Expert knowledge for Azure Deployment Environments development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when defining environment.yaml, configuring dev centers/projects…
azure-business-process-tracking
Expert knowledge for Azure Business Process Tracking development including deployment. Use when creating CI/CD pipelines, automating builds, running tests, and deploying tracking solutions via DevOps tools, and other Azure Business Process Tracking related development tasks. Not for Azure Monitor (use azure-monitor)…
define-slo-sli-sla
Establish Service Level Objectives (SLO), Service Level Indicators (SLI), and Service Level Agreements (SLA) with error budget tracking, burn rate alerts, and automated reporting using Prometheus and tools like Sloth or Pyrra. Use when defining reliability targets for customer-facing services, balancing feature…