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 punt-labs/beadlenpx agentmods add plugins/punt-labs/beadle/plugingit clone --depth 1 https://github.com/punt-labs/beadleGrade A, and why
beadle-dev 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": "beadle-dev",
"description": "Autonomous agent daemon with cryptographic owner control. Email communication via IMAP/SMTP with PGP trust model.",
"version": "0.16.5",
"author": {
"name": "Punt Labs",
"email": "[email protected]"
},
"mcpServers": {
"email": {
"type": "stdio",
"command": "beadle-email",
"args": [
"serve"
]
}
}
}
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 · 19 lines scan A 892709a137ad
beadle-dev is a plugin published in the GitHub repository punt-labs/beadle (3 stars, last pushed yesterday), 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
prfaq-dev
Amazon Working Backwards PR/FAQ process — generate professional LaTeX documents for product discovery and decision-making.
goalkeeper
Durable goal-following for Claude Code: contracts with definition-of-done, subagent judge gates, and linear chains.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…
cc-autopilot
Autonomous judge agents fix your app's debt, build what's missing, and verify every change through a browser or gate suite before it lands, then find the next thing and keep going until you say stop. Each fixer owns a file-disjoint slice of the tree, so no two can ever collide, and nothing unverified reaches git. A…
threatswarm-plugin
Complete offensive security operator workspace: 27 specialist agents, 6 engagement commands, 5 reference skill libraries, scope-gated hooks, and evidence logging for professional penetration testing and red-team operations.
erpaval
ERPAVal — autonomous software development workflow for Claude Code. Comprehensive standalone bundle: the erpaval workflow plus 10 vendored companion skills (product-discovery, research, ultraplan, tech-stack-builder, product-strategy, working-backwards, customer-research, meta-prompt-optimizer, product-design-shared…