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 catcatcatstudio/cat-skills --skill architectgit clone --depth 1 https://github.com/catcatcatstudio/cat-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.
[](https://agentmods.dev/skills/catcatcatstudio/cat-skills/architect)<a href="https://agentmods.dev/skills/catcatcatstudio/cat-skills/architect"><img src="https://agentmods.dev/badge/skills/catcatcatstudio/cat-skills/architect.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.00076 | $0.02571 |
| Opus 5 | $0.00038 | $0.01286 |
| Sonnet 5 | $0.00015 | $0.00514 |
| Haiku 4.5 | $0.00008 | $0.00257 |
Grade A, and why
architect 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 7d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staged Build Methodology
Drive software projects through a structured lifecycle that prevents the #1 AI coding failure: losing context on a big plan and missing pieces.
When NOT to use this skill
- Task is a quick script, one-off fix, or single-file change → just build it directly
- User wants to edit existing code, not plan a new project → edit directly
- Scope is entirely clear and fits in one session without a plan → skip the methodology
- User explicitly says "just do it" without wanting a plan → respect that
Quick Reference
| Phase | What happens | Gate to pass |
|---|---|---|
| 0 | Technical spike — validate riskiest constraint | PROJECT_STATE.md with validated constraint |
| 1 | Design notes — one per domain, no code | All domains covered, user confirms |
| 1.5 | Build order — dependency graph, stage sequence | _build-order.md reviewed + approved |
| 2+Execute | Write 2-3 stages → build → repeat | All tests green, stage committed |
Full methodology: references/methodology.md · Testing obligations: references/testing.md · Stage format: references/stage-template.md
Core rule: Never work from one giant plan. Atomize into stages small enough to hold entirely in context, execute correctly, and validate before moving on.
Invocation
| Input | Action |
|---|---|
Bare (/architect) |
Ask: "New project or resuming an existing one?" |
| With project description | Assess scope (see Scaling Tiers), then start Phase 0 |
resume or project name |
Run Resume Protocol below |
Scaling Tiers
| Tier | Signal | Phases Used | Notes |
|---|---|---|---|
| Light | Single feature, 1-2 files, < 500 lines | Phase 0 (quick) → Phase 2 (1-2 stages) → Execute | Skip formal design notes. |
| Standard | Multi-component system, 3-8 stages | All phases | Full methodology. |
| Heavy | 8+ stages, multiple subsystems, external integrations | All phases + milestones | Group stages into milestones of 3-4. Milestone gate check between each. See references/methodology.md § Milestones. |
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.
- 7d ago First seen · 294 lines · 76 tokens per session scan A 6c1e97b48c3a
architect is a skill published in the GitHub repository catcatcatstudio/cat-skills (3 stars, last pushed 11d ago), licensed MIT. It adds 76 tokens to every session and 2,571 once invoked, about $0.0004 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
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…