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 BottleYo/model-economy --skill module-designgit clone --depth 1 https://github.com/BottleYo/model-economyWrote 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/bottleyo/model-economy/module-design)<a href="https://agentmods.dev/skills/bottleyo/model-economy/module-design"><img src="https://agentmods.dev/badge/skills/bottleyo/model-economy/module-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.00042 | $0.00319 |
| Opus 5 | $0.00021 | $0.00160 |
| Sonnet 5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
module-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
模块设计
寻找能让公共接口更小、内部能力更集中、未来改动更局部的最小结构改进。
边界
- 不得启动 subagent，不得改变任务分类、模型选择、角色或质量门。
- 不得自行提交、发布、创建 issue 或把结构建议直接扩张为重构项目。
- 不以文件数量、类数量或抽象层数衡量设计质量；优先观察调用方需要知道多少细节，以及一个需求会触及多少边界。
- 涉及新架构、广泛影响或高风险边界时，返回
cost-aware-development重新分类，不自行批准。
方法
- 明确需要改善的行为和当前公共接口。
- 检查知识是否泄漏到调用方、同一规则是否散落、一个概念是否需要多处同步修改。
- 比较保持现状、收拢到现有模块、建立新边界三种选择，只保留能降低真实维护成本的方案。
- 给出最小建议：目标边界、接口变化、迁移影响、验证方式和不应顺手处理的范围。
没有可证实的结构收益时，明确建议不改。
What ships with it
1 file 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 · 25 lines · 42 tokens per session scan A 0c1a894fe5c1
module-design is a skill published in the GitHub repository BottleYo/model-economy (5 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 319 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
reviewee-judgment
Evaluates received review results before they generate work by separating problems from proposed fixes and comparing responses in a fixed decision order. Use whenever review results may lead to artifact changes; does not produce reviews.
recipe-review
Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, and applies user-approved corrections.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, and applies user-approved React corrections.
recipe-quality-profile
Proposes and, after user confirmation, creates or maintains docs/project-context/quality.yaml from repository-specific review requirements. Use when asked to generate or update a repository quality profile.
ai-development-guide
Root-cause discipline, proportionate impact analysis, and implementation completeness assurance. Use when fixing bugs, reviewing code quality, refactoring, making technical decisions, or performing quality assurance.
coding-rules
Repository-aware implementation rules for minimal design surface, contract safety, representative patterns, and verifiable changes. Use when implementing, refactoring, or reviewing code.