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 skills add Skyfox-io/Memex --skill ideagit clone --depth 1 https://github.com/Skyfox-io/MemexWrote 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/skyfox-io/memex/idea)<a href="https://agentmods.dev/skills/skyfox-io/memex/idea"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/idea/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/skills/skyfox-io/memex/idea"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/idea.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.00084 | $0.00551 |
| Opus 5.5 | $0.00034 | $0.00220 |
| Sonnet 5.5 | $0.00017 | $0.00110 |
| Haiku 4.5 | $0.00008 | $0.00055 |
Grade A, and why
idea 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 1mo 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
Memex - Capture Idea
Wikilink rule: In any markdown you write, reference files as [[filename]].
Quick-capture to the scratch inbox. Routing happens later (session-end or on demand).
Step 1: Resolve the inbox path
Search order:
- Workspace config table, if present.
scratch/ideas.md.ideas.mdat workspace root.
If none exist, create scratch/ideas.md (or ideas.md at root if there's no scratch/ folder).
Step 2: Capture
Take the idea text from $ARGUMENTS or the user's message. If genuinely ambiguous, ask one clarifying question. Otherwise just capture.
Append:
### [brief title] - YYYY-MM-DD
[idea in 1-3 sentences]
-> Suggested route: [domain folder from Hub Map, or "unrouted"]
If _MANIFEST.md exists, read its Hub Map to suggest a route. Otherwise mark unrouted.
Step 3: Confirm
Idea captured: "[brief title]"
-> Suggested route: [domain path or "unrouted"]
Saved to: [resolved path]
Don't route now. Routing is session-end's job, or runs when the user asks.
Gotchas
- Don't route eagerly. If the route looks obvious, still write to the inbox. Batched routing at session-end avoids fragmenting the inbox and lets the user review.
- Inbox file missing mid-session. If the file vanished (renamed, moved), don't recreate silently in a new location. Re-resolve via the search order above; only create fresh when nothing matches.
- Not for claims or decisions. A claim about state ("Alice now leads X") goes in the relevant file's content (and surfaces via the closets
claims:field). A locked-in choice goes indecisions.md. The inbox is for unprocessed sparks. - One idea per entry. If the user dumps three ideas at once, append three blocks, not one merged blob. Routing works per-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.
- 1mo ago First seen · 57 lines · 84 tokens per session scan A 8a7cd909ed25
idea is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 551 once invoked, about $0.0003 per session on Opus 5.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
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML…
insights
Use when the user types /weekly or /monthly, asks for a weekly or monthly journal review or retrospective, asks 'how was my week' or 'how was my month', or wants trends, anomalies, or patterns across recent journal entries. Also fires when regenerating an insight report for a past week or month. NOT for writing…
setup-brain
Set up or upgrade an AI-powered Obsidian vault. Interviews you, builds your vault structure (or works with what you already have), creates your CLAUDE.md memory file, installs tools, and gets you journaling — all in one conversation. Also has a repair/upgrade path for existing users.
second-brain-mapping
Use when the user wants to map or remap their second brain, refresh the vault's queryable metadata index, extract structured frontmatter from typed notes (books, meetings, people, journals, goals), fill wikilink gaps, or surface cross-type insights and patterns no single file shows. Triggers: /second-brain-mapping…
sunday-review
Use when the user asks for the weekly meta-review or Sunday wrap-up of their week and vault: says /sunday, /sunday-review, 'let's do the weekly review,' 'Sunday review,' 'review my week,' 'weekly retro,' 'week in review,' 'end-of-week review,' or wants journals, patterns, vault health, and stale decisions reviewed…
coach
Use when the user says /coach (today, week, month, profile, log), asks what to do today for training, asks for a workout, weekly training plan, or longevity plan, wants to log a finished workout or check lift progression (PR, plateau, deload), or a scheduled morning task fires to drop today's workout into the…