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 agentmods add skills/rjmurillo/ai-agents/software-engineering-librarynpx skills add rjmurillo/ai-agents --skill software-engineering-librarygit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/software-engineering-library)<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/software-engineering-library"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/software-engineering-library.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.00201 | $0.01001 |
| Opus 5 | $0.00101 | $0.00500 |
| Sonnet 5 | $0.00040 | $0.00200 |
| Haiku 4.5 | $0.00020 | $0.00100 |
Grade A, and why
software-engineering-library 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 yesterday.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Engineering Library
This skill routes software engineering design work to deeper book-derived references without loading them on every turn.
For the everyday default, none loads on every turn and code-quality, pragmatic-programmer and unified-software-engineering load on code files; open a reference here only when the task needs that specific book's depth (start with one, add a second only when it changes a decision).
Triggers
architecture reviewdomain modeling bounded contextrefactoring code smells legacy code low test coverage old file characterization testsexternal API calls queues retries timeouts circuit breaker bulkheadtransactions event ordering data consistency schema evolution module interface shape
When Each Reference Applies
- Use
references/clean-architecture.mdwhen dependency direction, layer ownership, or boundary placement drives the decision. - Use
references/philosophy-of-software-design.mdwhen module depth, interface shape, or complexity hiding drives the decision. - Use
references/domain-driven-design.mdwhen the work models a domain, splits bounded contexts, or translates across contexts. - Use
references/enterprise-patterns.mdwhen persistence, repositories, unit-of-work, transactions, or application service orchestration are central. - Use
references/refactoring.mdwhen changing internal structure, addressing code smells, or preserving behavior while improving shape. - Use
references/working-with-legacy-code.mdwhen the code is hard to test, poorly covered, or needs seams and characterization tests before change. - Use
references/data-intensive-applications.mdwhen state, storage, schema evolution, consistency, ordering, or delivery semantics are central. - Use
references/release-it.mdwhen production resilience, timeouts, circuit breakers, bulkheads, retries, and operational failure modes are central.
Task To Reference Router
| Task | Reference |
|---|---|
| Architecture / layer boundaries | references/clean-architecture.md, references/philosophy-of-software-design.md |
| Domain modeling / bounded contexts | references/domain-driven-design.md |
| Persistence / repository / unit-of-work | references/enterprise-patterns.md |
| Refactoring / code smells | references/refactoring.md |
| Legacy code / seams / characterization tests | references/working-with-legacy-code.md |
| Data systems / consistency / schema evolution | references/data-intensive-applications.md |
| Production resilience / timeouts / bulkheads | references/release-it.md |
What ships with it
8 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.
- references/clean-architecture.md 15 KB
- references/data-intensive-applications.md 14 KB
- references/domain-driven-design.md 19 KB
- references/enterprise-patterns.md 11 KB
- references/philosophy-of-software-design.md 14 KB
- references/refactoring.md 13 KB
- references/release-it.md 18 KB
- references/working-with-legacy-code.md 14 KB
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.
- yesterday First seen · 73 lines · 201 tokens per session scan A f2a91304df5a
software-engineering-library is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 201 tokens to every session and 1,001 once invoked, about $0.0010 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
ci-cd-pipeline-builder
../../../engineering/skills/ci-cd-pipeline-builder/SKILL.md.
claude-coach
../../../engineering/claude-coach/skills/claude-coach/SKILL.md.
code-tour
../../../engineering/code-tour/skills/code-tour/SKILL.md.
codebase-onboarding
../../../engineering/skills/codebase-onboarding/SKILL.md.
nw-platform-engineering-foundations
Foundational platform engineering knowledge from key references -- Continuous Delivery, SRE, Accelerate, Team Topologies, Chaos Engineering, and Secure Delivery. Load when contextual grounding in platform engineering theory is needed.
yaml
Skill "yaml" from dhaupin/vant, covering yaml, when to use, what to do, 1. syntax and 2. anchors.