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/the-senior-dev/senior-dev-skillsWrote 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/the-senior-dev/senior-dev-skills/marketplace)<a href="https://agentmods.dev/plugins/the-senior-dev/senior-dev-skills/marketplace"><img src="https://agentmods.dev/badge/plugins/the-senior-dev/senior-dev-skills/marketplace/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/the-senior-dev/senior-dev-skills/marketplace"><img src="https://agentmods.dev/badge/plugins/the-senior-dev/senior-dev-skills/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
senior-dev-skills marketplace 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 1mo 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": "senior-dev-skills",
"owner": {
"name": "theSeniorDev"
},
"plugins": [
{
"name": "senior-dev-skills",
"source": {
"source": "github",
"repo": "the-senior-dev/senior-dev-skills"
},
"description": "Senior-level Claude Code skills by theSeniorDev"
}
]
}The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 1mo ago First seen · 16 lines scan A 4ad7a1b7f68a
senior-dev-skills marketplace is a plugin published in the GitHub repository the-senior-dev/senior-dev-skills (19 stars, last pushed 4mo 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-08-30.
Other plugins, from other repositories
mindrally-skills
265+ Claude Code skills covering every major framework, language, and development practice.
suede-code
Code quality subset: one-pass review plus an A-F ship verdict (suede-code), deep findings with TypeScript, React, Next.js, OWASP, and database checklists (suede-code-review), a grade-only verdict with instant-F triggers and grade caps (suede-code-grader), and CI branch protection that gates the merge (suede-ci-gate).
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
adversarial-review
Requires a task result to survive two consecutive independent adversarial reviews before completion.
aio-code-review
Runs an adaptive, project-aware code-review workflow and carries Google's engineering code-review playbook it applies. The workflow profiles the project, detects its real lint/type-check/test tooling and house conventions, reviews on two tracks (mechanical + semantic 8-dimension rubric), adversarially verifies each…
aio-codeflow
Understand, plan, debug, and review code as one coordinated workflow — codebase discovery, dependency mapping, implementation planning, root-cause debugging, and pre-merge review.