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/Eigenwise/eigenwise-toolshedWrote 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/eigenwise/eigenwise-toolshed/sidequest)<a href="https://agentmods.dev/plugins/eigenwise/eigenwise-toolshed/sidequest"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/sidequest/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/eigenwise/eigenwise-toolshed/sidequest"><img src="https://agentmods.dev/badge/plugins/eigenwise/eigenwise-toolshed/sidequest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
sidequest 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": "sidequest",
"version": "5.11.2",
"description": "A local work board and orchestration loop for Claude Code. Every task saved as a ticket survives context compaction and new sessions, with instructions, status, and recorded discussion kept on the board. Categories route tickets to a model and effort; token-gated executors return verified work for review and integration. A self-hosted Kanban dashboard spans your projects.",
"author": {
"name": "Eigenwise",
"email": "[email protected]"
},
"homepage": "https://github.com/Eigenwise/eigenwise-toolshed/tree/main/plugins/sidequest",
"repository": "https://github.com/Eigenwise/eigenwise-toolshed",
"license": "MIT",
"keywords": [
"tickets",
"kanban",
"trello",
"board",
"issues",
"todo",
"dashboard",
"hooks",
"capture"
]
}
What it installs
The manifest is a name and a version. 5 skills, 13 agents, 1 MCP server travel with it, and installing the plugin installs all of them — 361 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill groom A 37 tokens
- Skill user-story A 60 tokens
- Skill sidequest A 41 tokens
- Skill verify-discipline A 44 tokens
- Skill board A 18 tokens
- Agent sidequest-exec-dispatch-readonly A 14 tokens
- Agent sidequest-diagnostic-probe A 13 tokens
- Agent sidequest-exec-medium A 11 tokens
- Agent sidequest-exec-readonly-medium A 13 tokens
- Agent sidequest-exec-readonly-xhigh A 14 tokens
- Agent sidequest-exec-readonly-low A 13 tokens
- Agent sidequest-exec-readonly-max A 13 tokens
- Agent sidequest-exec-high A 11 tokens
- Agent sidequest-exec-low A 11 tokens
- Agent sidequest-exec-max A 11 tokens
- Agent sidequest-exec-xhigh A 12 tokens
- Agent sidequest-exec-readonly-high A 13 tokens
- Agent sidequest-exec-dispatch A 12 tokens
- MCP server board A not measured
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 Changed 91161f32e9a0
- 2d ago Changed f1838c69f65e
- 7d ago Changed 83c2d9e71a79
- 8d ago Changed 7c00067eaab8
- 11d ago Changed 8c12fd860e93
- 12d ago Changed 7d0f94d57854
- 13d ago Changed 1a9d743b50c8
- 15d ago Changed 51c6ec330744
- 16d ago Changed 49b442ba2743
- 17d ago First seen · 24 lines scan A 29e15c7a662c
sidequest is a plugin published in the GitHub repository Eigenwise/eigenwise-toolshed (280 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
pm-execution
Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, and more.
pm-product-strategy
Product strategy skills for PMs: vision, strategy canvas, value propositions, lean canvas, business model canvas, SWOT, PESTLE, Ansoff Matrix, Porter's Five Forces, and monetization.
handbook-structured-plan-mode
Structured planning methodology for complex feature implementations through systematic task decomposition.
odin-core
Core ODIN gates every session runs: intent, scope, verification, and hand-off checks.
roadmap
Product management, roadmap analysis, and solution architecture with multi-agent orchestration.
jira-pack
Issue-tracker pack: /jira-fix takes a ticket link of any type, verifies tracker access, classifies it as a defect or a change, reproduces the defect or writes a failing acceptance test for the change, routes the work to core executors, comments back with evidence and moves the ticket to the QA column. Opt-in; requires.