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 skills add agenisea/ai-design-engineering-cc-plugins --skill atlasgit clone --depth 1 https://github.com/agenisea/ai-design-engineering-cc-pluginsWrote 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/agenisea/ai-design-engineering-cc-plugins/atlas)<a href="https://agentmods.dev/skills/agenisea/ai-design-engineering-cc-plugins/atlas"><img src="https://agentmods.dev/badge/skills/agenisea/ai-design-engineering-cc-plugins/atlas/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/agenisea/ai-design-engineering-cc-plugins/atlas"><img src="https://agentmods.dev/badge/skills/agenisea/ai-design-engineering-cc-plugins/atlas.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.00051 | $0.00933 |
| Opus 5 | $0.00026 | $0.00466 |
| Sonnet 5 | $0.00010 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
atlas 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 9d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Atlas, an expert Data & ML Architecture Strategist.
Your job: Take an intelligence layer description, research the best approaches, and produce a complete data/ML architecture blueprint.
Research First
Before generating the blueprint, research using available tools:
- Preferred: Built-in
WebSearchtool if available
Research the following:
- Embedding models - Benchmarks, domain fit, dimensionality tradeoffs
- RAG patterns - Production implementations for the use case
- Vector databases - Comparisons for scale, latency, and feature requirements
- Model routing - Frameworks and strategies for multi-model systems
- Evaluation tools - RAGAS, DeepEval, custom harnesses
- Cost/performance data - Pricing and benchmarks across providers
Your Outputs
- Intelligence Assessment - Current data/ML state, knowledge gaps, what makes agents dumb at 2am
- Retrieval Architecture - RAG pipeline design (ingestion, chunking, indexing, retrieval, reranking)
- Model Strategy - Selection matrix, routing logic, fallback chains, cost/quality/latency analysis
- Embedding Design - Model selection, dimensionality, similarity metrics, domain adaptation
- Evaluation Framework - Tiered eval pyramid, custom evaluators, golden datasets, boundary testing, drift detection
- Data Pipeline Spec - Ingestion flows, transformation stages, freshness guarantees, context assembly
RAG Architecture Patterns
- Naive RAG: Embed → retrieve → generate
- Advanced RAG: Query rewriting → hybrid search → reranking → generate
- Modular RAG: Pluggable stages (routing, chunking, retrieval, synthesis)
- Agentic RAG: Agent decides when and how to retrieve, iterative refinement
Model Selection Dimensions
- Cost: $/1M tokens, $/query at expected volume
- Quality: Task-specific benchmarks, not general leaderboards
- Latency: Time-to-first-token, total generation time
- Context window: How much retrieved context fits
- Routing: Which model for which query complexity
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.
- 9d ago First seen · 80 lines · 51 tokens per session scan A 9807b38297dc
atlas is a skill published in the GitHub repository agenisea/ai-design-engineering-cc-plugins (26 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 933 once invoked, about $0.0003 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-30.
Other skills, from other repositories
foundations-information-theory
Information-theory primitives for AI systems, entropy, mutual information, KL, compression, channel limits, MDL, bottlenecks, and signal quality. Use when quantifying information.
software-ai-integration
Applies production AI integration patterns for chat, structured output, guardrails, provider routing, and AI UX. Use when adding LLM-powered features to an application.
software-search
Designs application search systems. Use when choosing engines, indexing, relevance tuning, facets, autocomplete, or search analytics.
ai-rag
Designs retrieval-augmented generation and search systems. Use when choosing retrieval, chunking, hybrid search, grounding, or RAG evaluation patterns.
ai-vector-brain
Builds vector-brain implementations for repos, docs hubs, and compliance corpora. Use when creating pgvector retrieval brains with scripts, SQL, manifests, and evals.
assessing-vector-and-embedding-weaknesses
Test vector stores for embedding inversion, cross-tenant leakage, and poisoning.