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/pyyush/goalWrote 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/pyyush/goal/goal)<a href="https://agentmods.dev/plugins/pyyush/goal/goal"><img src="https://agentmods.dev/badge/plugins/pyyush/goal/goal/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/pyyush/goal/goal"><img src="https://agentmods.dev/badge/plugins/pyyush/goal/goal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
goal 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 2mo 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "goal",
"version": "0.2.0",
"description": "Persistent objective lifecycle for Claude Code: set a goal once, Claude pursues it across turns until it is verifiably done.",
"author": {
"name": "goal maintainers"
},
"license": "MIT",
"keywords": ["goal", "objective", "persistence", "agent", "autonomy", "lifecycle"],
"commands": ["./goal.md"],
"mcpServers": {
"goal": {
"command": "bash",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp/run-goal-server.sh"],
"env": {
"GOAL_PLUGIN_ROOT": "${CLAUDE_PLUGIN_ROOT}"
}
}
},
"channels": [
{ "server": "goal" }
]
}
What it installs
The manifest is a name and a version. 2 skills, 4 hooks travel with it, and installing the plugin installs all of them — 279 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 2mo ago First seen · 25 lines scan A fd3ba2b7ff41
goal is a plugin published in the GitHub repository pyyush/goal (1 stars, last pushed 5mo 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-31.
Other plugins, from other repositories
rate-limit-monitor
Statusline segment + prompt-submit guard for Claude Code's 5-hour and 7-day usage limits. Shows live usage %, and at a configurable threshold it blocks new prompts (with an override) so a long token-heavy task doesn't get cut off mid-run.
hermitd-feed
Scheduled briefs for Hermit from sources you choose, with story tracking, weekly summaries, and source-quality checks.
feed-hermit
Scheduled briefs for Hermit from sources you choose, with story tracking, weekly summaries, and source-quality checks.
claude-code-hermit
Your own local Claude Tag, in the Claude app, Discord, Telegram, or a custom Claude Code channel.
brewcode
Brewcode - Claude Code authoring toolkit: skill, agent and rule creation and sync, semantic code search (semble), project conventions, E2E tests, generated review and domain-team skills, setup dashboard, post-compact plan re-anchor.
hush
Quieter sessions for Claude Code: less narration, shorter tool output and concise answers focused on the result.