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 cenconq25/claude-code-app-studio --skill map-systemsgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/map-systems)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/map-systems"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/map-systems/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/cenconq25/claude-code-app-studio/map-systems"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/map-systems.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.00049 | $0.01985 |
| Opus 5 | $0.00024 | $0.00992 |
| Sonnet 5 | $0.00010 | $0.00397 |
| Haiku 4.5 | $0.00005 | $0.00198 |
Grade A, and why
map-systems 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 5d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map Systems
Translates the concept doc into a graph of systems with dependencies and a recommended design order. The systems index that this skill writes is the authoritative list /design-system reads to figure out what to write next.
Output: design/systems-index.md
Purpose / When to Run
Run when:
design/concept.mdis complete and approved- The team needs a single source of truth for what systems exist
- New systems were discovered mid-design and the index needs updating
Argument next is a shortcut: re-reads the index and shows the next system in the priority order without rebuilding the whole list.
Inputs
design/concept.md(required)design/design-bible.mdif present.claude/docs/technical-preferences.md- Existing
design/systems-index.mdif updating
Outputs
design/systems-index.md
Phase 1: Argument Handling
If argument is next:
- Read
design/systems-index.md - Find the highest-priority system with status
Not started - Print: "Next system to design: (priority , layer ). Run
/design-system <name>to start." - Done — do not rebuild the index.
Otherwise, full mapping flow:
- If
design/systems-index.mdexists, ask whether to refresh it, append new systems only, or rebuild from scratch.
Phase 2: Read Concept
Read design/concept.md. Extract:
- The one-liner
- The MVP scope (in v1) and cuts (out of v1)
- The primary metric
- The riskiest assumption
If concept doc is missing, stop:
"No
design/concept.mdfound. Run/brainstormfirst."
If concept is fragmentary (sections empty), warn: "Concept doc has [N] empty sections. Mapping with incomplete concept will produce a brittle systems list — recommend completing the concept first."
Phase 3: Propose System List
For a typical mobile app, propose a candidate list. Adapt to what the concept says — never copy this list verbatim. Use it as a checklist to make sure no obvious system is forgotten.
Standard candidate categories:
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.
- 5d ago First seen · 266 lines · 49 tokens per session scan A 58b0a31b1d20
map-systems is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 1,985 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.