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/coroboros/agent-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/coroboros/agent-skills/coding-skills)<a href="https://agentmods.dev/plugins/coroboros/agent-skills/coding-skills"><img src="https://agentmods.dev/badge/plugins/coroboros/agent-skills/coding-skills/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/coroboros/agent-skills/coding-skills"><img src="https://agentmods.dev/badge/plugins/coroboros/agent-skills/coding-skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
coding-skills 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": "coding-skills",
"description": "Project scaffolding and eight-axis code review with contextual validation and JSONL output",
"source": "./",
"strict": false,
"skills": [
"./skills/scaffold",
"./skills/code-ultrareview"
]
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 124 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 marketplace.json#coding-skills 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 Changed 68d173c4c62a
- 1mo ago First seen · 10 lines scan A 55b71495d0bb
coding-skills is a plugin published in the GitHub repository coroboros/agent-skills (4 stars, last pushed today), 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-09-03.
Other plugins, from other repositories
agentsys marketplace
25 specialized plugins for AI workflow automation - task orchestration, PR workflow, slop detection, code review, drift detection, enhancement analysis, documentation sync, unified static analysis, durable memory, negative behavior memory, skill and system prompt curation, perf investigations, topic research, agent…
product-discovery-suite
Decide what is worth building, who it serves, and what a useful first version must do.
architecture-suite
Understand the system you have and choose changes with clear boundaries, tradeoffs, and recovery paths.
ai-dev-team
A specialist agent team plus an enforced, proportional workflow: role agents that self-route to deep references, cross-cutting process skills for the gate contract, work-item lifecycle, proving a change landed, review tiering, model selection, research method, grounded-answer audit and pull-request completion, and…
pr-workflow
PR and issue lifecycle — structured planning (CEO/Eng gates), PR creation, code review, issue triage, session handoffs.
nah
NAH, Not Another Harness: ticket-driven build loop with cross-vendor code review (architect session, tk tickets, one-ticket-at-a-time developer subagent, GPT reviewer via pi).