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.
/plugin marketplace add jasonm4130/claude-skillsnpx agentmods add plugins/jasonm4130/claude-skills/adrgit clone --depth 1 https://github.com/jasonm4130/claude-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/jasonm4130/claude-skills/adr)<a href="https://agentmods.dev/plugins/jasonm4130/claude-skills/adr"><img src="https://agentmods.dev/badge/plugins/jasonm4130/claude-skills/adr.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
adr 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 4d 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": "adr",
"description": "Turns an intent into a grounded, cited, build-ready ADR (docs/adr/YYYY-MM-DD-<slug>.md) — every claim cited, load-bearing decisions surfaced to the human — then hands it to the subagent-driven-development loop. Front-end for adr → sdd.",
"version": "0.5.1",
"author": { "name": "Jason Matthew", "email": "[email protected]" },
"homepage": "https://github.com/jasonm4130/claude-skills",
"repository": "https://github.com/jasonm4130/claude-skills",
"license": "MIT",
"keywords": ["adr", "architecture-decision-record", "grounding", "subagent-driven-development", "sdd"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 120 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.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.
- 4d ago First seen · 11 lines scan A e8b020b9e95f
adr is a plugin published in the GitHub repository jasonm4130/claude-skills (5 stars, last pushed 5d 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-31.
Other plugins, from other repositories
gh-review-loop
Clears AI reviewer feedback on your PR: reads real review-thread state, sweeps the sibling instances the reviewer missed, gates every push on your repo's own tests, then requests re-review — hard-capped so it can never spam the PR. Works with Codex out of the box, or any reviewer bot you configure.
tessary marketplace
Plugin marketplace listing 2 plugins: evals, crew.
evals
Connect your repo to evals.tessary.ai and work with your evals from the coding agent — wire trace ingestion over OTLP, tag your call sites, assess graders, query failing traces, read the cases and root-cause reports the platform opens, and author per-call-site SOP-conformance files (derive from the code, reconcile on…
crew
A multi-agent dev harness: hand it a goal and the orchestrator triages, implements, reviews, responds to feedback, and keeps docs and knowledge current — autonomously, up to a review-ready PR. Use the individual skills directly, or /crew:run to let it decide what to do.
heading-core
Sovereignty and session core: the prime/state-check/checkpoint skills, the standalone sovereignty guard hooks, and the session checkpoint system - a context-usage sensor, a threshold offer, a pre-compaction brief that states what the summary must keep verbatim, a redacted post-compact save, and a resume injector, all…
heading-ops
Ops and thinking: draft an implementation plan (create-plan), reason through a hard decision (deep-think), and run a structural editorial pass (editorial-review). Reserved (data/daemon/key-bound): dashboard, radar, queue, sync, next, recall, council.