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/johnlarkin1/claude-code-extensions/ics-generatornpx skills add johnlarkin1/claude-code-extensions --skill ics-generatorgit clone --depth 1 https://github.com/johnlarkin1/claude-code-extensionsWhat 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.00095 | $0.03845 |
| Opus 5 | $0.00048 | $0.01922 |
| Sonnet 5 | $0.00019 | $0.00769 |
| Haiku 4.5 | $0.00010 | $0.00384 |
Grade A, and why
ics-generator 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 423 lines · 95 tokens per session scan A 7027c63b4e08
ics-generator is a skill published in the GitHub repository johnlarkin1/claude-code-extensions (21 stars, last pushed 1mo ago), with no licence file. It adds 95 tokens to every session and 3,845 once invoked, about $0.0005 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
schedule
Manages recurring and one-off scheduled tasks. Session-scoped scheduling via CronCreate/CronDelete/CronList. Documents the cloud path for tasks that need to survive machine sleep or network drops.
do
Unified router that auto-routes user intent to the right direct action, skill, orchestrator, or explicit Operation Control plan. Classifies input by scope, complexity, persistence needs, and parallelism, then dispatches to the cheapest path that can handle it: direct command, skill, marshal, archon, or fleet. Single…
collab-conflict
까다로운 동료·소통빌런과 부딪힐 때 감정 상하지 않게 대응하고 거리를 지키도록 도와주는 스킬입니다. '이 사람 어떻게 대하지', '자꾸 떠넘기는 동료', '거절하는 법', '직장 인간관계 스트레스', '갈등 대응'처럼 말하면 됩니다. 유형별 대응 전략, 감정과 사안 분리, 정중한 거절, 관계 거리 두기로 직장 갈등을 소모전이 아니라 관리 가능한 문제로 바꿉니다.
collab-negotiation
1:1 면담을 준비하고, 상대를 설득하거나 무언가를 요청·협상할 때 대화를 설계해 주는 스킬입니다. '면담 준비해줘', '이거 어떻게 설득하지', '연봉 협상 어떻게', '부탁하는 법', '정중하게 요청하고 싶어'처럼 말하면 됩니다. 면담 목표 설정 → 상대 입장 파악 → 설득 구조 → 요청·거절 화법 → 합의·후속의 5단계로 관계를 지키며 원하는 걸 얻는 대화를 만듭니다.
collab-feedback-loop
피드백을 건설적으로 주고, 받은 피드백을 감정 상하지 않게 소화하도록 도와주는 스킬입니다. '피드백 어떻게 줘야 해', '부정적 피드백 받았는데 속상해', '피드백 전달하는 법', '중간 점검 요청하고 싶어'처럼 말하면 됩니다. SBI 구조로 건설적 피드백을 설계하고, 받은 피드백을 사실과 감정으로 분리해 소화하며, 먼저 피드백을 요청하는 법까지 다룹니다.
collab-meeting
회의가 산으로 가지 않게 아젠다를 짜고 결론까지 끌고 가는 진행을 도와주는 스킬입니다. '회의 아젠다 짜줘', '이 회의 어떻게 진행하지', '회의가 자꾸 산으로 가', '의사결정 회의 준비', '회의록 정리'처럼 말하면 됩니다. 목적 정의 → 아젠다 설계 → 진행 규칙 → 의사결정 → 회의록·후속 액션의 5단계로 결론이 남는 회의를 설계합니다.