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/ktncodes/icm-template/icm-syncnpx 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.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.00052 | $0.01616 |
| Opus 5 | $0.00026 | $0.00808 |
| Sonnet 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 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 — 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.
- 4d 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 (52 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,616 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…