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 paruff/uFawkesAI --skill architecture-decompositiongit clone --depth 1 https://github.com/paruff/uFawkesAIWrote 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/paruff/ufawkesai/architecture-decomposition)<a href="https://agentmods.dev/skills/paruff/ufawkesai/architecture-decomposition"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/architecture-decomposition/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/paruff/ufawkesai/architecture-decomposition"><img src="https://agentmods.dev/badge/skills/paruff/ufawkesai/architecture-decomposition.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.00027 | $0.00598 |
| Opus 5 | $0.00014 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
architecture-decomposition 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Architecture Decomposition
Load trigger:
"load architecture-decomposition skill"> DORA: Cap 3 (AI-Accessible Internal Data) Token cost: Low
Purpose
Break the specification into logical architectural components.
Responsibilities
- Identify major system components
- Identify data flows between components
- Identify external dependencies
- Identify boundaries and responsibilities
Inputs
specification.md
Outputs
architecture.json
Decomposition Rules
Component Identification
- Each component has a single, clear responsibility
- Components are loosely coupled
- Components communicate through defined interfaces
- No god components (doing everything)
Data Flow
- Data flows are unidirectional where possible
- Synchronous and asynchronous flows identified
- Data transformation points identified
- Error flows documented
External Dependencies
- External APIs identified
- Databases identified
- Message queues identified
- Third-party services identified
Boundaries
- Layer boundaries defined (UI, Service, Data)
- Trust boundaries identified
- Integration boundaries identified
Architecture Patterns
| Pattern | Use When |
|---|---|
| Monolith | Simple domain, small team, fast iteration |
| Microservices | Complex domain, independent scaling, team autonomy |
| Event-Driven | Async workflows, loose coupling, audit trail |
| CQRS | Read/write optimization, complex queries |
| Serverless | Variable load, event-driven, minimal ops |
Output Format
{
"components": [
{
"name": "Component Name",
"purpose": "What it does",
"responsibility": "What it owns",
"layer": "ui | service | data | infrastructure",
"dependencies": ["Other Component"],
"external_dependencies": ["External API"]
}
],
"data_flows": [
{
"from": "Component A",
"to": "Component B",
"type": "sync | async",
"data": "What is transferred"
}
],
"boundaries": [
{
"type": "layer | trust | integration",
"description": "Boundary description"
}
]
}
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 · 110 lines · 27 tokens per session scan A db753ffbcd96
architecture-decomposition is a skill published in the GitHub repository paruff/uFawkesAI (2 stars, last pushed 17d ago), licensed MIT. It adds 27 tokens to every session and 598 once invoked, about $0.0001 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
planning-with-files
Persistent file-based planning for multi-step AI-agent work. Keeps taskplan.md, findings.md, and progress.md on disk; lifecycle hooks inject selected project planning context. Automatic recovery reads project planning files only. Explicit session-catchup.py --metadata reads same-project local agent session records and…
infrastructure-overview
Top-level skill for the research template infrastructure layer. Use in Cursor, Claude Code, or similar agents when editing or importing anything under infrastructure/, understanding the two-layer architecture, or wiring build/validation/rendering/publishing. Covers module discovery, import patterns, thin…
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
infrastructure-llm
Skill for the LLM infrastructure module providing local Large Language Model integration via Ollama. Covers client initialization, prompt templates, output validation, manuscript review generation, conversation context, and CLI usage. Use when querying LLMs, generating manuscript reviews, validating LLM outputs, or…
infrastructure-tools
Skill for the tools module — discovery, validation, scope, and private-sidecar symlink sync for the top-level tools/ directory (executable entry points such as scripts, skills, and agents stored as passive manifests with scripts/ directories). Use when discovering tools (discovertools), resolving a tool path…
template-academic-paper
Template-native manuscript planning, outline, drafting, revision, formatting, citation check, and AI-use disclosure routing. USE WHEN the user asks to write, outline, revise, format, or prepare a paper inside the Research Project Template.