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 ktnCodes/icm-template --skill icm-syncgit clone --depth 1 https://github.com/ktnCodes/icm-templateWrote 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/ktncodes/icm-template/icm-sync)<a href="https://agentmods.dev/skills/ktncodes/icm-template/icm-sync"><img src="https://agentmods.dev/badge/skills/ktncodes/icm-template/icm-sync/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/ktncodes/icm-template/icm-sync"><img src="https://agentmods.dev/badge/skills/ktncodes/icm-template/icm-sync.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.00052 | $0.01616 |
| Opus 5.5 | $0.00021 | $0.00646 |
| Sonnet 5.5 | $0.00010 | $0.00323 |
| Haiku 4.5 | $0.00005 | $0.00162 |
Grade A, and why
icm-sync 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ICM Sync
Scan the current workspace and re-sync the ICM routing files (IDENTITY.md and CONTEXT.md) so any LLM session can navigate the workspace correctly.
Step 1: Locate ICM Root
Find the workspace root by searching upward from the current directory for IDENTITY.md. If no IDENTITY.md exists, report: "No ICM workspace found. Run /icm-scaffold first." and stop.
Read these files to understand what is currently documented:
IDENTITY.md— folder map tree, rules, any stage or project tablesCONTEXT.md— routing table, session start protocol, pipeline stages (virtual or physical)CLAUDE.md(if it exists) — model adapter synced from IDENTITY.md
Step 2: Scan the Actual Workspace
List the workspace contents on disk:
- Note every folder and key file at the root level
- For each folder mentioned in IDENTITY.md, list its current subfolders
- For stage folders (if full mode), list each stage's contents
- For
_config/andreferences/folders, list files present
Step 3: Diff — Find Gaps
Compare what's on disk vs. what's documented in IDENTITY.md and CONTEXT.md. Identify:
New items (on disk, NOT in IDENTITY.md):
- New top-level folders
- New subfolders inside documented folders
- New
_config/orreferences/files - New stage folders (full mode)
Stale items (in IDENTITY.md, NOT on disk):
- Folder paths in the map that no longer exist
- Stage folders referenced in routing that were removed
- _config/ files listed that were deleted
Routing drift (CONTEXT.md references paths that don't exist):
- Routing table entries pointing to missing folders
- Virtual stage inputs referencing deleted files
- Session start protocol referencing files that moved
Status drift (may need updating):
- Projects or sections marked as one status but clearly changed (e.g., empty folder now has real content)
Step 4: Resolve New Items
For each new folder or file found that isn't in IDENTITY.md:
If it has a CONTEXT.md or README.md: read it to determine purpose.
If it doesn't: infer from folder name and contents.
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 · 170 lines · 52 tokens per session scan A ad948ce78b10
icm-sync is a skill published in the GitHub repository ktnCodes/icm-template (76 stars, last pushed 6mo ago), licensed MIT. It adds 52 tokens to every session and 1,616 once invoked, about $0.0002 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…