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/skyfox-io/memex/wikilinksnpx skills add Skyfox-io/Memex --skill wikilinksgit 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/wikilinks)<a href="https://agentmods.dev/skills/skyfox-io/memex/wikilinks"><img src="https://agentmods.dev/badge/skills/skyfox-io/memex/wikilinks.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.00070 | $0.00905 |
| Opus 5 | $0.00035 | $0.00452 |
| Sonnet 5 | $0.00014 | $0.00181 |
| Haiku 4.5 | $0.00007 | $0.00090 |
Grade A, and why
wikilinks 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memex - Wikilinks
Wikilink rule: When referencing any file in any markdown content you write or edit, always use [[filename]] wikilink format. Never use plain text filenames.
Two modes: verify broken links, then suggest plain-text → [[wikilink]] conversions.
Step 1: Find workspace root
Run WORKSPACE_ROOT=$(pwd) && echo "$WORKSPACE_ROOT" via Bash.
Step 2: Verify wikilink integrity
Run the script at ${CLAUDE_SKILL_DIR}/scripts/verify-wikilinks.py:
python3 "${CLAUDE_SKILL_DIR}/scripts/verify-wikilinks.py" "$WORKSPACE_ROOT" --skip .claude .obsidian .git
If the script can't be found, report: "Wikilink script not found - skipping." Do not silently pass.
Report:
Broken links: 0
or:
BROKEN WIKILINKS ([count] found):
[file]: [[broken-link]]
Offer fixes:
- Target renamed → update the link
- Target deleted → remove the link or replace with plain text
- Target never existed → flag for the user to decide
Step 3: Suggest wikilink conversions
Re-run the script with --suggest:
python3 "${CLAUDE_SKILL_DIR}/scripts/verify-wikilinks.py" "$WORKSPACE_ROOT" --suggest --skip .claude .obsidian .git
Scans markdown for plain-text mentions of existing filenames that aren't already [[wrapped]]. Handles exact and hyphenated-to-space matches. Skips code blocks, URLs, and frontmatter.
Step 4: Present conversion suggestions
WIKILINK CONVERSIONS ([count] suggested):
marketing-plan.md:
Line 12: "see the budget spreadsheet" -> "see the [[budget]] spreadsheet"
Line 34: "based on the roadmap" -> "based on the [[roadmap]]"
meeting-notes.md:
Line 5: "discussed pitch deck" -> "discussed [[pitch-deck]]"
Apply all [count] conversions? (or review one by one)
If the user confirms, apply the conversions. If they want to review, go through each one and ask.
Step 5: Report summary
Wikilinks report:
Broken links: [count fixed or 0]
Conversions applied: [count]
Total wikilinks in workspace: [count]
Files scanned: [count]
Obsidian graph: [count] nodes, [count] edges
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 98 lines · 70 tokens per session scan A 9b5d277ebf58
wikilinks is a skill published in the GitHub repository Skyfox-io/Memex (17 stars, last pushed 2mo ago), licensed MIT. It adds 70 tokens to every session and 905 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
obsidian
Comprehensive guidelines for Obsidian.md plugin development including ESLint rules from eslint-plugin-obsidianmd v0.4.1, TypeScript best practices, memory management, API usage (requestUrl vs fetch), UI/UX standards, popout window compatibility, community.obsidian.md submission process, and Scorecard optimization. Use…
paid-ads
When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, or other ad platforms. Also trigger on "PPC", "paid media", "ROAS", "CPA", "ad campaign", "retargeting", "audience targeting", "Google Ads setup", "Facebook Ads strategy", "LinkedIn Ads". Covers campaign…
sales-enablement
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also trigger on "sales deck", "pitch deck", "one-pager", "leave-behind", "objection handling", "ROI calculator", "demo script", "talk track", "sales playbook", "proposal template". For competitor battle…
aia-generation
Run an AI impact assessment — structured intake, risk analysis, UK regulatory classification (UK GDPR / DPA 2018, ICO AI guidance, sector-specific UK regulation), EU AI Act analysis where EU nexus exists, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed…
cold-start-interview
Run the cold-start interview — learns your UK AI governance practice and writes /.claude/plugins/config/uk-legal-plugins/ai-governance-legal-uk/CLAUDE.md from your AI policy, a reference impact assessment, and key vendor AI agreements. Use when the practice profile is missing or contains [PLACEHOLDER] markers, or when…
integration-management
Post-completion M&A integration tracker — phased workplan, consent tracking, contract assignment at scale, weekly status reports. Initialises from whatever deal artefacts are available (purchase agreement, deal summary, closing checklist) and connects to deal-context.md and closing-checklist.yaml from the M&A…