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 cookieMonsterDev/agents-skills --skill architecture-templategit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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.
![agentmods badge for [object Object]](/badge/skills/cookiemonsterdev/agents-skills/architecture-template.svg?v=0-120-C){kind=icon}
[](https://agentmods.dev/skills/cookiemonsterdev/agents-skills/architecture-template)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/architecture-template"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/architecture-template.svg" alt="Measured on agentmods" 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.00120 | $0.01131 |
| Opus 5 | $0.00060 | $0.00566 |
| Sonnet 5 | $0.00024 | $0.00226 |
| Haiku 4.5 | $0.00012 | $0.00113 |
Grade C, and why
[object Object] scanned grade C with 1 finding 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 6d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- Delete the "Examples" section below if this skill has no bundled code examples (e.g. a skill about system-design trade-offs or architectural principles may not need one). --> 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.
{Skill Title}
Ground {domain} answers in the reference files bundled with this skill instead of improvising definitions. Each {item, e.g. "pattern" / "principle"} has a reference file explaining it{, and a folder of runnable examples in popular languages — delete this clause if the skill has no code examples}.
When to Use
- The user names {an item} directly ("show me the {item} in {language}")
- The user describes a problem that maps to {an item} ("{example problem phrasing}")
- The user asks to compare {items} ("{item A} vs {item B}?")
- The user wants existing code or design refactored toward {an item}
Workflow
- Identify the {item(s)} from the user's question using the catalog below.
- Read the reference file at
references/<item>.mdfor the explanation, applicability, trade-offs, and related {items}. - Read the language example at
examples/<item>/<item>.<ext>when the user works in (or asks for) a specific language. Adapt it to their domain rather than pasting the generic example verbatim. (Delete this step if the skill has no code examples.) - Answer with: what the {item} does, when to use it (and when not to), and {code/guidance} adapted to the user's context.
If the user's problem does not match any {item} cleanly, say so — do not force {an item} where a simpler solution fits.
{Domain} Catalog
Group {items} into the categories that make sense for this domain (creational/structural/behavioral, principle/practice, layer/tier, etc.). One table per category.
{Category 1}
{One-line description of what this category of items has in common.}
| {Item} | Intent | Reference |
|---|---|---|
| {Item A} | {What it does, in one line} | references/{item-a}.md |
| {Item B} | {What it does, in one line} | references/{item-b}.md |
{Category 2}
{One-line description of what this category of items has in common.}
What ships with it
3 files 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.
- 6d ago First seen · 80 lines · 120 tokens per session scan C aac7043a5c0e
[object Object] is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 17d ago), licensed MIT. It adds 120 tokens to every session and 1,131 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…