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/adamw7/tools/solid-principlesnpx skills add adamw7/tools --skill solid-principlesgit clone --depth 1 https://github.com/adamw7/toolsWhat 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 | $0.00084 | $0.01420 |
| Opus 5 | $0.00042 | $0.00710 |
| Sonnet 5 | $0.00017 | $0.00284 |
| Haiku 4.5 | $0.00008 | $0.00142 |
Grade A, and why
solid-principles 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOLID Principles Skill
Review and apply SOLID in the tools reactor. The heuristics below are the fast
path; long before/after code lives in examples.md next to this file — load
it only when a worked example would actually help.
Quick reference
| Letter | Principle | One-liner |
|---|---|---|
| S | Single Responsibility | One class = one reason to change |
| O | Open/Closed | Open for extension, closed for modification |
| L | Liskov Substitution | Subtypes must be substitutable for base types |
| I | Interface Segregation | Many specific interfaces beat one general one |
| D | Dependency Inversion | Depend on abstractions, not concretions |
S — Single Responsibility
One reason to change.
Detect: imports from unrelated domains · a name containing "And", "Manager" or "Handler" · methods that use none of the fields · you cannot describe the class in one sentence without "and".
Fix: Extract Class / Move Method.
Here: an AdoptionStep is one stage of the adoption and nothing else;
ClaudeCodeEnforcerRule.report(...) is the one exit point every enforcer rule
funnels its violations through; the uniqueness core knows nothing about its MCP
adapter (ArchUnit fails the build if it learns).
O — Open/Closed
New behaviour arrives as a new class, not an edit to an old one.
Detect: an if/else or switch on a type or status that keeps growing ·
adding a feature means editing a core class.
Fix: Strategy, Template Method, Decorator, Factory.
Here: GitHubRepoAdopter composes a List<AdoptionStep>, so a new stage is
a new step, not a branch; a new tree output format is a new
ProjectTreeSerializer; BudgetedContext decorates any Context instead of
teaching Finder about budgets; AbstractFinder template-methods the
depth-bounded traversal and lets subclasses supply only
findDirectDependencies.
L — Liskov Substitution
A subtype may not surprise a caller holding the base type.
What ships with it
2 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.
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 · 143 lines · 84 tokens per session scan A 5580ceab15d1
solid-principles is a skill published in the GitHub repository adamw7/tools (11 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 1,420 once invoked, about $0.0004 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-30.
Other skills, from other repositories
union-type-wrappers
Add typed getters and setters over BinaryData properties that represent TypeSpec union types in generated Java models. Use when generated classes expose BinaryData for union-typed fields and you need ergonomic, type-safe accessors instead.
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
run-tests
Run project tests using Maven (mvn). Use when the user asks to run tests.
search-m2
Search for Java classes inside Maven dependencies in /.m2. Use when the user asks to locate classes or inspect JARs. Cross-reference pom.xml files in the current directory to resolve dependency names/versions.
using-process-tool
Describes how to correctly use 'process' tool.