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/grainulation/grainulatorWrote 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/grainulation/grainulator/marketplace)<a href="https://agentmods.dev/plugins/grainulation/grainulator/marketplace"><img src="https://agentmods.dev/badge/plugins/grainulation/grainulator/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/grainulation/grainulator/marketplace"><img src="https://agentmods.dev/badge/plugins/grainulation/grainulator/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
grainulation-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 24d 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": "grainulation-marketplace",
"owner": {
"name": "Grainulation",
"email": "[email protected]"
},
"metadata": {
"description": "Evidence and verification tools for model-assisted work",
"version": "1.0.0"
},
"plugins": [
{
"name": "grainulator",
"source": {
"source": "url",
"url": "https://github.com/grainulation/grainulator.git"
},
"description": "Evidence and verification for model-assisted work",
"version": "2.0.4",
"author": {
"name": "Grainulation"
},
"homepage": "https://grainulator.app",
"repository": "https://github.com/grainulation/grainulator",
"license": "MIT",
"keywords": ["research", "grainulator", "claims", "evidence", "briefs"],
"category": "research",
"tags": [
"research-sprints",
"analysis",
"documentation",
"decision-making"
]
}
]
}
The plugins it lists here
This marketplace lists 2 plugins 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.
- 24d ago Changed 0c0a77fe0359
- 1mo ago Changed 36df9ebc9372
- 1mo ago First seen · 37 lines scan A 8351052e4a93
grainulation-marketplace is a plugin published in the GitHub repository grainulation/grainulator (86 stars, last pushed 2d 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
clawdbod
Stay active while coding. Injects fitness breaks into your Claude Code sessions — micro-challenges between prompts and scaled workouts during long-running tasks. All workout data stays on your machine, exportable to CSV or JSON.
filip-podstavec marketplace
Plugin marketplace listing 1 plugin: claude-leverage.
hyperclaude
Push Claude Code beyond stock. Skills, agents, Codex collab — opinionated and personal.
requirements-generator
Generates structured requirements documents from a project idea or feature description, including functional requirements, non-functional requirements, Gherkin acceptance criteria, edge cases, and out-of-scope items.
skill-bus
The skill for connecting skills. Connect context, conditions, and other skills to any skill — no modification required.
agent-based-development
Full async multi-agent development workflow: Planning → Design → Dev → Security/Tech Review loop with file-based handoffs and release-branch Git model.