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/mnthe/hardworker-marketplaceWrote 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/commands/mnthe/hardworker-marketplace/insights)<a href="https://agentmods.dev/commands/mnthe/hardworker-marketplace/insights"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/insights/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/commands/mnthe/hardworker-marketplace/insights"><img src="https://agentmods.dev/badge/commands/mnthe/hardworker-marketplace/insights.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.00712 |
| Opus 5 | $0.00005 | $0.00356 |
| Sonnet 5 | $0.00002 | $0.00142 |
| Haiku 4.5 | $0.00001 | $0.00071 |
Grade A, and why
insights 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage insights collected from the current session.
Determine Action
Parse the argument to determine which action to perform:
| Argument | Action |
|---|---|
| (none) | Show current session's insights |
extract |
Launch insight-extractor agent to convert insights |
clear |
Delete current session's insights |
Argument provided: $ARGUMENTS
Action: Show Current Session Insights (default)
If no argument provided or argument is empty:
- Get current session ID from
CLAUDE_SESSION_IDenvironment variable - Check if insights file exists at
~/.claude/knowledge-extraction/{session-id}/insights.md - If exists, read and display the contents
- If not exists, inform that no insights have been collected this session
Display format:
📝 Insights for session {session-id}
{content of insights file}
Total: {count} insight(s)
Tip: Run `/insights extract` to convert these into reusable components.
Action: Extract (/insights extract)
If argument is "extract":
- Check if insights file exists at
~/.claude/knowledge-extraction/{session-id}/insights.md - If no insights, inform user
- If insights exist, launch the
insight-extractoragent using Task tool:- Agent analyzes collected insights
- Proposes extraction targets (Skill, Command, Agent, CLAUDE.md)
- Presents proposals for user approval
- Creates approved components
- Cleans up session directory after successful extraction
Action: Clear (/insights clear)
If argument is "clear":
- Get current session ID
- Check if session directory exists at
~/.claude/knowledge-extraction/{session-id}/ - If exists:
- Count insights in insights.md
- Delete the entire session directory (insights.md + state.json)
- Confirm deletion
- If not exists, inform no insights to clear
Output:
🗑️ Cleared {count} insight(s) from session {session-id}.
Storage Structure
All insights are stored in a centralized location in the home directory:
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.
- 9d ago First seen · 107 lines · 11 tokens per session scan A 43cce1289d03
insights is a command published in the GitHub repository mnthe/hardworker-marketplace (4 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 712 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-31.
Other commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.