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 specsnl/agent-specsnpx agentmods add plugins/specsnl/agent-specs/marketplacegit clone --depth 1 https://github.com/specsnl/agent-specsGrade A, and why
specs 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 2d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "specs",
"owner": {
"name": "Specsnl Team",
"email": "[email protected]"
},
"metadata": {
"description": "A collection of plugins for Specs"
},
"plugins": [
{
"name": "laravel",
"source": "./plugins/laravel",
"version": "0.0.20",
"description": "A Specs Laravel specific plugin"
},
{
"name": "docker",
"source": "./plugins/docker",
"version": "0.0.7",
"description": "A Specs Docker specific plugin"
},
{
"name": "linear",
"source": "./plugins/linear",
"version": "0.0.4",
"description": "A Specs plugin for creating Linear issues from raw client input"
},
{
"name": "code",
"source": "./plugins/code",
"version": "0.0.4",
"description": "A Specs plugin with cross-language code authoring conventions"
},
{
"name": "github",
"source": "./plugins/github",
"version": "0.0.9",
"description": "A GitHub-specific plugin for Specs"
},
{
"name": "crit",
"source": {
"source": "git-subdir",
"url": "https://github.com/tomasz-tomczyk/crit.git",
"path": "integrations/claude-code"
},
"description": "Review and comment on plans, code diffs, and frontend elements, then send feedback directly to your agent."
},
{
"name": "git-workflow",
"source": {
"source": "git-subdir",
"url": "https://github.com/paulinevos/claude-stuff.git",
"path": "plugins/git-workflow"
},
"description": "Atomic-commit Git workflow skills: folding changes into the right commit (amend/edit/fixup), conflict resolution, reflog-based undo, and biWhat 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.
- 2d ago First seen · 61 lines scan A b57ea98a2e5a
specs is a plugin published in the GitHub repository specsnl/agent-specs (2 stars, last pushed 16d 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
humanizer
Rewrite AI-sounding text so it reads naturally without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.