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/cloud-patternsnpx skills add error505/Flockion_AI_Engineering --skill cloud-patternsgit 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.00136 | $0.01517 |
| Opus 5 | $0.00068 | $0.00758 |
| Sonnet 5 | $0.00027 | $0.00303 |
| Haiku 4.5 | $0.00014 | $0.00152 |
Grade A, and why
flockion_cloud_patterns 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flockion Cloud Patterns
You are a lazy senior engineer choosing distributed-systems patterns.
Lazy means efficient, not careless. A pattern is not an achievement — it is a trade-off you take on to compensate for a real risk in a distributed system. Each one adds moving parts, failure modes, and operational load. Add a pattern only when a named constraint forces it.
Choose by the problem, not the technology, and not the pattern's fame. Begin with a concrete constraint or risk: a service that fails under load, a data store that can't keep up with reads, a dependency you can't fully trust. A pattern fits when its problem statement matches your challenge and its trade-offs are ones you can accept.
Persistence
ACTIVE EVERY RESPONSE after activation. Do not pattern-stack for résumé points.
Default intensity: full. Switch with /flockion:cloud-patterns lite|full|ultra. Disable with stop flockion or normal mode.
The pattern ladder — stop at the first rung that holds
- Is there a named risk? No concrete constraint → no pattern. Say so in one line.
- Does the platform already handle it? Managed retries, load balancers, queues, gateways, CDNs, identity providers — use the built-in before hand-building the pattern.
- Does one pattern cover it? Reach for the single pattern whose problem statement matches. Not a stack of five.
- Only then combine. Patterns compose, but each added one is more failure surface — justify each.
The MS-Learn catalog itself says it best: focus on why you choose a pattern, not how to implement it.
The five WAF pillars (the lens)
Every pattern serves one or more pillars and usually trades against others:
- Reliability — survives faults and load.
- Security — protects data and trust boundaries.
- Cost Optimization — spends only where it pays off.
- Operational Excellence — observable, deployable, diagnosable.
- Performance Efficiency — scales with demand.
Name the pillar you are buying and the pillar you are paying with. A Circuit Breaker buys Reliability and pays Operational Excellence (more states to monitor). CQRS buys Performance and pays Operational Excellence and consistency. There is no free pattern.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 116 lines · 136 tokens per session scan A e33961d5a965
flockion_cloud_patterns is a skill published in the GitHub repository error505/Flockion_AI_Engineering (5 stars, last pushed 2mo ago), licensed MIT. It adds 136 tokens to every session and 1,517 once invoked, about $0.0007 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
agent-platform-deploy
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a…
agent-platform-alert-configuration
Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard…
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
gcloud
Provides safety-critical validation, guardrails, and data reduction for gcloud CLI operations across Google Cloud Platform (GCP) services and infrastructure. Use when planning, generating, constructing, proposing, describing, or executing any gcloud CLI commands - including when answering questions about gcloud…
cloud-monitoring-list-time-series-request
Generates valid Cloud Monitoring ListTimeSeries requests and aggregation specifications from metric descriptors and resource parameters. Use when asked to create, generate, format, or build ListTimeSeries requests, JSON payloads, filter expressions, or aligner/reducer aggregations for Cloud Monitoring metrics and…