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 skills/eigenwise/eigenwise-toolshed/boardnpx skills add Eigenwise/eigenwise-toolshed --skill boardgit 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/skills/eigenwise/eigenwise-toolshed/board)<a href="https://agentmods.dev/skills/eigenwise/eigenwise-toolshed/board"><img src="https://agentmods.dev/badge/skills/eigenwise/eigenwise-toolshed/board.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.00160 |
| Opus 5 | $0.00009 | $0.00080 |
| Sonnet 5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
board 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 4d 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
Launching the sidequest board:
!node "${CLAUDE_PLUGIN_ROOT}/bin/sidequest.js" dashboard
The board should now be open in your browser (it shows every project's tickets, live). Report the URL printed above so the user can click it if the browser didn't pop up.
If nothing was printed above, open the board by running the sidequest dashboard command yourself with
the Bash tool — the resolved CLI path is provided in your context by the sidequest hook (it looks like
node "…/bin/sidequest.js"). Then report the URL.
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.
- 4d ago First seen · 18 lines · 18 tokens per session scan A e645fcc36bf5
board is a skill published in the GitHub repository Eigenwise/eigenwise-toolshed (37 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 160 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
clickup
Use when managing ClickUp tasks, sprints, or comments via the cup CLI tool. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, listing spaces and lists, opening tasks in browser…
dashboard
This skill should be used when the user asks to "/dashboard", "open the dashboard", "show me my pipeline visually", "launch the dashboard", or wants a browser-based view of their job-search pipeline. Launches a local Python server that serves a React + Mantine SPA reading from userdata/companies//meta.md…
forge-clarify
Clarify and validate Forge issues before planning — reproduce bugs via browser, verify UX expectations for features, capture evidence screenshots. Use this skill after triage (confirmed status) to ensure the issue is well-understood before writing an implementation plan. Triggers on: /forge-clarify, clarifying issues…
wfdash
Serve wayfinder maps held in GitHub Issues as a local browser dashboard — one map drawn as a dependency DAG, plus an overview of every map across every repo. Use when the user asks what to work on next, wants to see a map's shape or frontier, wants to read a resolved ticket's decision, or types /wfdash. Also use for…
loop-hardening-contract
Harden repeated delivery loops with evidence-based harness stripping, immutable runtime-path sprint packets, and broken-window revalidation without automatic revert. Use for Cardputer, browser, CI, runtime, or production work split into repeated sprints.
adaptive-suite
A continuously adaptive skill suite that empowers Clawdbot to act as a versatile coder, business analyst, project manager, web developer, data analyst, and NAS metadata scraper. It intelligently discovers free resources, adapts to user context, and ensures reliable, proven guida…