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/closetheloops/moradin/capturenpx skills add CloseTheLoops/moradin --skill capturegit clone --depth 1 https://github.com/CloseTheLoops/moradinWrote 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/closetheloops/moradin/capture)<a href="https://agentmods.dev/skills/closetheloops/moradin/capture"><img src="https://agentmods.dev/badge/skills/closetheloops/moradin/capture.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.00030 | $0.00587 |
| Opus 5 | $0.00015 | $0.00293 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
moradin-capture 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 3d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
moradin:capture
Capture an external source as a reference. Capture EVERYTHING notable, not just what fits the current project. Project-specific filtering happens later at distillation time.
When invoked
/moradin:capture <url> (or /moradin:capture <description> if not URL)
The operator saw something interesting and wants to record it permanently.
What you do
-
WebFetch the URL (or read source if local). Read README + key sections.
-
List ALL notable concepts in your reply. Don't pre-filter for current project relevance. Show the operator a full inventory of what's in the source:
- Concept A: [one paragraph]
- Concept B: [one paragraph]
- Concept C: [one paragraph]
- ...
-
For each concept, propose tags:
topics: from the 8-tag taxonomy (harness, memory, eval, llm, agent, arch, workflow, tooling)applies_to: which projects might use it (universal, godtech, trading, future)
-
Ask the operator to confirm or edit the tags. Don't auto-write — get a green light.
-
Note what you deliberately skipped — tactical setup details, deeply specific code, or items fundamentally irrelevant.
-
Write the reference file at
memory/references/<source_name>.mdusingtemplates/reference.template.mdas scaffold. Include:- Frontmatter: name, description, topics, applies_to, type=reference, url, captured (date), last_verified (date)
- Body: "What it is" + "Notable concepts" (full inventory) + "What I deliberately skipped"
-
Update indexes. Run
python scripts/refresh_indexes.pyso_INDEX.mdreflects the new file. -
Confirm to operator with the file path.
Capture discipline (the rule that protects against losing useful concepts)
The big failure mode: filtering concepts at capture time based on current project. Don't. Concepts that don't fit GodTech today may fit trading next month. Capture full inventory.
Don't
- Don't summarize away interesting-but-tangential concepts. Capture them.
- Don't auto-assign tags without operator confirmation.
- Don't write attribution like "inspired by X" — once captured, the concepts are ours.
- Don't capture a reference if we've already captured the same source — update the existing file instead.
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.
- 3d ago First seen · 57 lines · 30 tokens per session scan A e7bff0a9aee3
moradin-capture is a skill published in the GitHub repository CloseTheLoops/moradin (2 stars, last pushed 25d ago), licensed MIT. It adds 30 tokens to every session and 587 once invoked, about $0.0002 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 skills, from other repositories
llm-wiki-company-flow-audit
Map company/team information flows into an LLM-Wiki adoption plan. Use when the user asks where team knowledge lives, which streams can be automated, how Confluence/Jira/Slack/Drive changes stay synced, how fragile review is, how confidential data is handled, or whether maintenance cost is worth the benefit.
llm-wiki-capture-pipeline
Design cross-channel capture architecture and named connector runbooks for LLM-Wiki. Use when the user wants an inbox/raw topology, metadata contract, dedupe boundary, triage handoff, privacy defaults, capture-to-ingestion flow, or Telegram/email/Slack/PDF/GitHub/voice connector rules.
llm-wiki-orient
Explain the LLM-Wiki pattern, its raw/wiki/schema architecture, how it differs from RAG, GraphRAG and agent memory, and what ready-made solution families exist. Use when the user asks what LLM-Wiki is, whether it is worth adopting, what OpenWiki/wiki memory means, or how the ecosystem fits together.
llm-wiki-zero-to-working-wiki
Create a first useful LLM-Wiki from zero. Use when the user wants a zero-to-working-wiki walkthrough, first vault, first source ingest, first reusable query, first lint report, or a visible demo loop before a larger rollout; route full workflow installs to llm-wiki-setup.
wiki-lint
Run structural and trust health checks for an LLM-Wiki vault. Use for broken links, orphan pages, missing provenance, stale claims, contradiction reports, taxonomy drift, protected-section edits, and review queue generation.
llm-wiki-agent-memory-bridge
Decide what belongs in LLM-Wiki versus agent memory, AGENTS.md, CLAUDE.md, Auto Memory, Codex project memory, or other runtime memories. Use when instruction files are bloated, domain facts live in agent memory, or the user wants clean memory boundaries.