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.
npx agentmods add plugins/svy04/ballast/marketplace/plugin marketplace add svy04/ballastgit clone --depth 1 https://github.com/svy04/ballastGrade A, and why
ballast 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": "ballast",
"description": "Builds up to a goal in a field you have no expertise in — learns the foundations it needs and keeps every solved path for the next goal.",
"owner": {
"name": "svy04"
},
"plugins": [
{
"name": "ballast",
"source": "./",
"description": "Builds up to a goal in a field you have no expertise in: splits it into the foundations that goal actually needs, mobilizes what you already hold, learns what is missing, and leaves every solved path behind for the next goal. Nothing is called done until a check passes."
}
]
}
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.
- yesterday First seen · 15 lines scan A 53b27c883c7f
ballast is a plugin published in the GitHub repository svy04/ballast (71 stars, last pushed 7d 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
smartcompact
Plugin marketplace listing 1 plugin: smartcompact.
smartcompact
Human-in-the-loop context compaction for Claude Code. You choose which turns survive; a SessionStart hook re-injects them deterministically after every compact and resume.
lossless-code
DAG-based lossless context management for Claude Code.
lossless-code
DAG-based lossless context management for Claude Code. Every message from every session is persisted in a SQLite vault with FTS5 search. Summaries form a directed acyclic graph - nothing is ever lost.
fable-orchestrator
Fable 5-first multi-agent orchestration for Claude Code: a token-frugal chair profile with tier routing (Sonnet 5 carries the volume, Opus 5 the hard slices), chair-sized effort per worker, a Requirements Ledger, guard hooks that enforce the discipline, and automatic teammate reaping. A clarification phase grills an…
orchestrator
Token-frugal multi-agent orchestration for Claude Code, built for a Claude Fable 5 chair: Fable plans and decides, Sonnet 5 carries the volume, Opus 5 takes the hard slices and escalations — each worker's effort sized by the chair — and a two-tier verification valve guards the close. When the Fable limit runs dry, an…