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 sanmak/specopsnpx agentmods add plugins/sanmak/specops/specopsgit clone --depth 1 https://github.com/sanmak/specopsGrade A, and why
specops 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 yesterday.
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": "specops",
"description": "Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.",
"version": "1.8.0",
"author": {
"name": "Sanket Makhija"
},
"repository": "https://github.com/sanmak/specops",
"homepage": "https://github.com/sanmak/specops",
"license": "MIT",
"keywords": [
"spec-driven",
"specifications",
"workflow",
"requirements",
"design",
"tasks"
]
}
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.
- yesterday First seen · 20 lines scan A 3d8b53d0af05
specops is a plugin published in the GitHub repository sanmak/specops (49 stars, last pushed 29d 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
memorix
Shared workspace memory for Claude Code and other AI coding agents.
draft-plugins
Plugin marketplace listing 1 plugin: draft.
draft
Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.
figma-design-system-to-design-md
Figma design system to design.md — Extract Figma design system into a structured design.md document. Automatically detects token files, style configs, and Figma MCP data to generate comprehensive design system documentation covering Colors, Typography, Spacing, Border Radius, Elevation, Responsive, and more.
ijfw
Plugin marketplace listing 1 plugin: ijfw.
commit-commands
Smart commit message generation and git workflow commands.