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/a-lottes/aSPARKWrote 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/a-lottes/aspark/marketplace)<a href="https://agentmods.dev/plugins/a-lottes/aspark/marketplace"><img src="https://agentmods.dev/badge/plugins/a-lottes/aspark/marketplace/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/a-lottes/aspark/marketplace"><img src="https://agentmods.dev/badge/plugins/a-lottes/aspark/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aspark marketplace 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": "aspark",
"description": "Marketplace for aSPARK — an agile AI product team for Claude Code (Specify, Plan, Act, Review, Keep).",
"autoUpdate": true,
"owner": {
"name": "Andreas Lottes",
"email": "[email protected]"
},
"plugins": [
{
"name": "aspark",
"source": "./",
"description": "An agile AI product team for Claude Code — Specify, Plan, Act, Review, Keep."
},
{
"name": "aspark-guard",
"source": {
"source": "github",
"repo": "a-lottes/aSPARK-guard"
},
"description": "Optional. Enforces the SPARK gates in code rather than in prompt, and records every .spark/ write with its hash. Silent in projects without .spark/."
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.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.
- 1mo ago Changed · +8 lines ed78a8d37c4f
- 1mo ago First seen · 17 lines scan A 2e53945fbd3a
aspark marketplace is a plugin published in the GitHub repository a-lottes/aSPARK (24 stars, last pushed 3d 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
x-dev-pipeline
Structured dev workflow with spec, user-global risk RAG, task breakdown, execution, verify, qa-gate, fix loops, and audits.
pocketto
Pocket-driven development skills: structured subagent delegation, bug hunting, iterative planning, code review workflows, and an opt-in education mentor mode for Claude Code.
python-dev
Python development workflow with architecture design, coding guidelines, testing patterns, and specialized review agents.
claude-skills
Skills and agents that add lifecycle gates around planning and building with Claude Code, with each kind of job running on its own model and effort: ground a plan in reality, verify a finished diff with fresh eyes, audit injected context, set up per-repo permissions so you can run auto mode with confidence, and turn a.
branch-recap
Tells you what your branch actually changed — what was done, why, and what deserves a second look, instead of the diff — then files the fixes into the commits they belong to.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.