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/jordancoin/codingskills/solidnpx skills add JordanCoin/codingskills --skill solidgit clone --depth 1 https://github.com/JordanCoin/codingskillsWhat 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.00065 | $0.01426 |
| Opus 5 | $0.00032 | $0.00713 |
| Sonnet 5 | $0.00013 | $0.00285 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
solid 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 3d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOLID Principles
Before Applying
If .agents/stack-context.md exists, read it first. Apply this principle using idiomatic patterns for the detected stack. For framework-specific details, use context7 MCP or web search — don't guess.
Principle
Five design principles that produce modular, testable, and resilient systems. While originally framed for object-oriented design, the underlying ideas apply to any paradigm — functions, modules, services, or components.
Why This Matters in Production
SOLID code is change-friendly code. Production systems change constantly — new features, bug fixes, integrations, scaling. Systems designed with SOLID principles absorb change locally rather than requiring cascading modifications. This means fewer regressions, faster feature delivery, and smaller blast radius when things go wrong.
S — Single Responsibility Principle
A module should have one, and only one, reason to change.
Every module, function, or component should own exactly one piece of functionality. When a change request comes in, you should be able to predict which file needs editing without searching.
Violations look like:
- A function that validates input, queries the database, applies business logic, and formats the response
- A "utils" file that grows indefinitely because nothing else has a clear home
- A class that changes every time any feature in the system changes
Apply it:
- If a function does two things, split it into two functions
- If a module handles both "what to do" and "how to do it," separate policy from mechanism
- Name modules after their responsibility — if the name is vague ("Manager", "Helper", "Utils"), the responsibility is unclear
O — Open/Closed Principle
Software should be open for extension but closed for modification.
You should be able to add new behavior without modifying existing, working code. This doesn't mean you never touch existing code — it means you design so that the common extension points don't require it.
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.
- 3d ago First seen · 134 lines · 65 tokens per session scan A 75d5bce7809a
solid is a skill published in the GitHub repository JordanCoin/codingskills (7 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 1,426 once invoked, about $0.0003 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
refactor
Automated iterative code refactoring with swarm-orchestrated specialist agents including deep codebase discovery, confidence-scored code review, and security analysis. Use this skill when the user wants to improve existing code quality, clean up messy code, restructure, simplify, reduce tech debt, or perform…
refactoring
Improve code structure without changing behavior using proven refactoring patterns. Use when cleaning up code, reducing duplication, improving readability, or restructuring modules.
feature-dev
Guided feature development with swarm-orchestrated codebase exploration, multi-perspective architecture design, implementation, and quality review.
feature-dev
Guided feature development with swarm-orchestrated codebase exploration, multi-perspective architecture design, implementation, and quality review. Use this skill when the user wants to build a new feature, add new functionality, implement a capability, or create something that doesn't exist yet. Triggers on requests…
refactoring-patterns
Use this skill when improving existing code without changing its behavior. It defines when and how to refactor safely.
delphi-rest-apis-horse
Desenvolvimento de microserviços e APIs REST com o framework minimalista Horse em Delphi. Rotas, controllers, middlewares, gerenciamento de memória e tratamento de parâmetros.