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/sodam-ai/SoDam-WikiMateWrote 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/sodam-ai/sodam-wikimate/wikimate-summarize)<a href="https://agentmods.dev/commands/sodam-ai/sodam-wikimate/wikimate-summarize"><img src="https://agentmods.dev/badge/commands/sodam-ai/sodam-wikimate/wikimate-summarize/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/sodam-ai/sodam-wikimate/wikimate-summarize"><img src="https://agentmods.dev/badge/commands/sodam-ai/sodam-wikimate/wikimate-summarize.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.00043 | $0.00346 |
| Opus 5 | $0.00022 | $0.00173 |
| Sonnet 5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
wikimate-summarize 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 10d 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
노트를 요약하거나 원자노트로 정리한다. "Wikimate Summarize" 스킬의 워크플로우를 따른다:
- 볼트 확정.
wikimate_summarize를action:"suggest"로 호출해 원문(body)과 현재 요약(current_summary)을 본다. - 원문을 근거로 200자 이내 한 줄
summary를 직접 작성한다(추측 금지). 필요하면atomic_note(제목+본문)도 함께 준비한다. - 계획을 보고하고
AskUserQuestion으로 [적용/건너뛰기/수정] 개별 승인을 받는다(비가역 편집). - 승인된 것만
wikimate_summarize를action:"apply", dry_run:false로 호출한다. 대상 노트의 본문(body)은 이 도구가 절대 수정하지 않는다. - 가능하면
wikimate-reviewer서브에이전트로 원문 왜곡 여부를 독립 검증한다(요약은 LLM 판단이 개입하는 유일한 쓰기라 환각 위험이 더 높음). - 결과(반영된 summary/원자노트 경로·백업)를 재확인 후 보고한다.
인자가 있으면 그 노트를 대상으로 시작한다: $ARGUMENTS
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.
- 10d ago First seen · 16 lines · 43 tokens per session scan A 476f9313e855
wikimate-summarize is a command published in the GitHub repository sodam-ai/SoDam-WikiMate (53 stars, last pushed 9d ago), licensed Apache-2.0. It adds 43 tokens to every session and 346 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-30.
Other commands, from other repositories
memory-store
Store an insight, decision, or pattern to memory.
dev
Runs Vendure in development mode. By default it starts three processes: the GraphQL server (ts-node ./src/index.ts), the worker (ts-node ./src/index-worker.ts), and the dashboard (a Vite dev server).
start
Runs a project that has already been compiled with vendure build.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.
triage-github
Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.
remember
Save text as a project memory in Rembric.