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 joinwell52-AI/CodeFlowMu-open --skill architect-system-designgit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/joinwell52-ai/codeflowmu-open/architect-system-design)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/architect-system-design"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/architect-system-design.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.00047 | $0.00231 |
| Opus 5 | $0.00023 | $0.00115 |
| Sonnet 5 | $0.00009 | $0.00046 |
| Haiku 4.5 | $0.00005 | $0.00023 |
Grade A, and why
architect-system-design 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.
What it actually says
Architect System Design
When to use
Use this skill before implementing changes that affect architecture, interfaces, MCP tools, Panel/API, lifecycle, events, schemas, or cross-module flow.
Rules
- Describe current architecture before proposing changes.
- Define interfaces and data flow.
- Compare alternatives.
- Keep design separate from implementation unless implementation is explicitly in scope.
Required output
Use docs/skills/architect-playbook/system-design.md.
Forbidden actions
- Do not treat local design as formal FCoP protocol change.
- Do not add runtime APIs without explicit implementation scope.
- Do not bypass ADMIN.
- Do not add adopted-pending
0003.
Minimal example
Problem: issue draft safety needs visibility
Interface: internal draft frontmatter safety_check
Risk: accidental public submission
Verification: draft contains admin_approved=false
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 · 38 lines · 47 tokens per session scan A 341f06dc03a8
architect-system-design is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 13d ago), licensed MIT. It adds 47 tokens to every session and 231 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-08-31.
Other skills, from other repositories
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.