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 pilotspace/ADDnpx agentmods add plugins/pilotspace/add/add-methodgit clone --depth 1 https://github.com/pilotspace/ADDGrade A, and why
add 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": "add",
"displayName": "ADD — AI-Driven Development",
"version": "3.2.0",
"description": "ADD (AI-Driven Development). The agent is the hands; ADD is the memory, judgment, and conscience — a lean, state-tracked skill that drives every change through one atomic task node: Direction → Build → Verify, red/green TDD built in, trusted on a recorded receipt rather than a plausible diff. State lives on disk, so context rot never survives a new session.",
"author": {
"name": "Tin Dang",
"email": "[email protected]"
},
"homepage": "https://github.com/pilotspace/ADD#readme",
"repository": "https://github.com/pilotspace/ADD",
"license": "MIT",
"keywords": [
"ai-driven-development",
"add",
"aidd",
"claude-code",
"skill",
"tdd",
"spec-driven",
"agent",
"methodology"
],
"skills": "./skill/"
}
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 · 26 lines scan A 2ca4f7443712
add is a plugin published in the GitHub repository pilotspace/ADD (19 stars, last pushed 4d 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
agent-toolkit
A collection of project-agnostic skills for common engineering tasks such as ticket refinement, planning, code reviews, agent memory hygiene, skill authoring, and more.
agent-toolkit
A collection of project-agnostic skills for common engineering tasks such as ticket refinement, planning, code reviews, agent memory hygiene, skill authoring, and more.
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
supply-chain-risk-auditor
Audit a project's npm, PyPI, and Go dependencies for supply-chain risk: version-matched advisories for direct dependencies and the full lockfile tree, abandoned upstreams, npm publisher concentration, and install scripts.
sharp-edges
Identify error-prone APIs, dangerous configurations, and footgun designs that enable security mistakes.
tripod
Plugin marketplace listing 1 plugin: tripod.