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/haabe/mycelium/ost-rendernpx skills add haabe/mycelium --skill ost-rendergit clone --depth 1 https://github.com/haabe/myceliumWhat 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.00060 | $0.04103 |
| Opus 5 | $0.00030 | $0.02051 |
| Sonnet 5 | $0.00012 | $0.00821 |
| Haiku 4.5 | $0.00006 | $0.00410 |
Grade A, and why
ost-render 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OST Render
Read-only render of .claude/canvas/opportunities.yml as a diagram or structured list. Second specialist in the render fleet (after /mycelium:diamond-render). See ${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md for shared conventions.
When NOT to use
- To BUILD or update the OST from research data →
/mycelium:ost-builder. This skill is read-only. - For cross-cutting opportunity→solution→cycle traceability view → dispatcher's
/mycelium:render --view traceability(deferred to Phase 4a–4d research-first methodology per architecture draft §10.2). - For ICE scoring of solutions →
/mycelium:ice-score.
Identifier exposure
Declared: YES
Scope (canvas surfaces touched)
| Canvas file | Identifier-bearing fields | Frequency |
|---|---|---|
.claude/canvas/opportunities.yml |
evidence_sources (URL-or-name strings); notes prose |
low (~1 in 10 cites a named individual rather than a URL) |
$MYCELIUM_ATTRIBUTION_REGISTRY env var (canonical) or .claude/memory/attribution-registry.yml (fallback) |
people: block with name+consent+note per entry |
read-only consultation; never rendered |
Per ${CLAUDE_PLUGIN_ROOT}/engine/render-conventions.md#hard-rule-consent--privacy-gate. Registry lives in roadmap-private memory by design — upstream Mycelium repo is public; registry contents must not ship there.
Rationale
OST shape is user-need-shaped (abstract opportunities and solutions), so identifier exposure is incidental rather than intrinsic. Identifier classes that can appear: cohort testers, peer practitioners, named external sources. All three go through the consent gate; external sources are typically public_ok already, but registry consultation is non-skippable to avoid drift.
Anon-label convention
Per engine/render-conventions.md#anon-label-convention:
- Cohort tester →
cohort-tester-N - Peer practitioner →
peer-practitioner-N - Unknown identifier class →
participant-N
Numbering resets per render; emit an in-render mapping footnote when redaction occurred so the operator can audit which anon label maps to which registry entry.
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.
- 2d ago First seen · 282 lines · 60 tokens per session scan A 76ad00695471
ost-render is a skill published in the GitHub repository haabe/mycelium (45 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 4,103 once invoked, about $0.0003 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
context-manager
Context management skill providing discovery, fetching, harvesting, extraction, compression, organization, cleanup, and guided workflows for project context.
prd-v05-technical-stack-selection
Determine technologies needed to build the product, making build/buy/integrate decisions during PRD v0.5 Red Team Review. Handles both greenfield and brownfield contexts. Triggers on requests to select tech stack, evaluate technologies, make build vs. buy decisions, discover existing assets, or when user asks "what…
prd-v06-architecture-design
Define how system components connect, establishing boundaries, patterns, and integration approaches during PRD v0.6 Architecture. Triggers on requests to design architecture, create system design, define component relationships, or when user asks "design architecture", "system design", "how do components connect?"…
prd-v08-monitoring-setup
Define monitoring strategy, metrics collection, and alerting thresholds during PRD v0.8 Deployment & Ops. Triggers on requests to set up monitoring, define alerts, or when user asks "what should we monitor?", "alerting strategy", "observability", "metrics", "SLOs", "dashboards", "monitoring setup". Outputs MON…
prd-v08-runbook-creation
Create operational playbooks for incident response, deployments, and maintenance during PRD v0.8 Deployment & Ops. Triggers on requests to create runbooks, document procedures, or when user asks "how do we handle incidents?", "runbook", "operational procedures", "on-call guide", "incident response", "maintenance…
prd-v09-feedback-loop-setup
Establish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market. Triggers on requests to set up feedback systems, capture user input, or when user asks "how do we collect feedback?", "feedback loop", "user research", "post-launch feedback", "customer feedback", "NPS"…