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.
git clone --depth 1 https://github.com/nimadorostkar/Claude-Skills-collectionWrote 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/plugins/nimadorostkar/claude-skills-collection/development)<a href="https://agentmods.dev/plugins/nimadorostkar/claude-skills-collection/development"><img src="https://agentmods.dev/badge/plugins/nimadorostkar/claude-skills-collection/development/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/plugins/nimadorostkar/claude-skills-collection/development"><img src="https://agentmods.dev/badge/plugins/nimadorostkar/claude-skills-collection/development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
development 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.
What it actually says
{
"name": "development",
"description": "Development — The craft that is independent of language: review, debugging, refactoring, design, and version control.",
"source": "./",
"strict": false,
"category": "development",
"skills": [
"./skills/development/architecture-decisions",
"./skills/development/bug-fix-protocol",
"./skills/development/cli-development",
"./skills/development/code-review",
"./skills/development/debugging",
"./skills/development/design-patterns",
"./skills/development/domain-modeling",
"./skills/development/git-workflow",
"./skills/development/legacy-modernization",
"./skills/development/refactoring",
"./skills/development/repository-exploration",
"./skills/development/simple-design",
"./skills/development/system-design"
]
}What it installs
The manifest is a name and a version. 13 skills travel with it, and installing the plugin installs all of them — 1,187 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill architecture-decisions A 88 tokens
- Skill debugging A 100 tokens
- Skill design-patterns A 98 tokens
- Skill domain-modeling A 92 tokens
- Skill legacy-modernization A 94 tokens
- Skill repository-exploration A 98 tokens
- Skill simple-design A 87 tokens
- Skill system-design A 95 tokens
- Skill bug-fix-protocol A 92 tokens
- Skill cli-development A 81 tokens
- Skill git-workflow A 85 tokens
- Skill refactoring A 82 tokens
- Skill code-review A 95 tokens
What ships with it
1 file beside marketplace.json#development 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.
- 3d ago First seen · 22 lines scan A 2b46cd3b0310
development is a plugin published in the GitHub repository nimadorostkar/Claude-Skills-collection (29 stars, last pushed 2d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-11.
Other plugins, from other repositories
technology
Architecture, engineering delivery, development discipline, debugging, review, and AI and automation systems.
code-intelligence
Codebase exploration, navigation, mapping, and static analysis tools for understanding unfamiliar codebases.
code-intelligence
Use when navigating or refactoring code with a language server - choosing between semantic (LSP), exact-text (rg), and fuzzy/semantic search; anchoring LSP calls by position; gating degraded results; and disclosing tool substitutions, in any language.
complexity-reducer
Reduce cyclomatic complexity and simplify functions.
double-check
Verify code correctness with systematic second-pass analysis.
quality-tools
Design review skills — SOLID and DRY rules for code reviews, with severities and a clear line between a real design finding and style taste.