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/revfactory/harness-engineering-with-cc/tip-formatnpx skills add revfactory/harness-engineering-with-cc --skill tip-formatgit clone --depth 1 https://github.com/revfactory/harness-engineering-with-ccWrote 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/revfactory/harness-engineering-with-cc/tip-format)<a href="https://agentmods.dev/skills/revfactory/harness-engineering-with-cc/tip-format"><img src="https://agentmods.dev/badge/skills/revfactory/harness-engineering-with-cc/tip-format.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.00042 | $0.00319 |
| Opus 5 | $0.00021 | $0.00160 |
| Sonnet 5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
tip-format 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.
What it actually says
tip-format
Claude Code 팁 문서의 표준 포맷.
파일 위치/이름
- 경로:
tips/<kebab-case>.md - 이름: 영문 소문자 + 하이픈 (예:
hooks-pre-tool-use.md)
프론트매터 (필수)
---
title: <한글 제목>
tags: [훅, 설정] # 카테고리 태그 1~3개
updated: YYYY-MM-DD
source: <출처 URL 또는 경로>
---
본문 구조
# <제목>
## 상황
어떤 문제/니즈에서 이 팁이 필요한가.
## 방법
단계별로 무엇을 한다.
## 예시
\`\`\`bash
# 실제 명령
\`\`\`
\`\`\`json
// 실제 설정
\`\`\`
## 주의점
함정, 버전 의존성, 검증이 필요한 부분.
규칙
- 한국어, 간결한 설명체.
- 코드블록 언어 명시.
- 한 파일 = 한 팁.
- 추측/미검증은 "확인 필요:" 프리픽스로 표시하거나 제외.
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 · 51 lines · 42 tokens per session scan A 46aefa2d1575
tip-format is a skill published in the GitHub repository revfactory/harness-engineering-with-cc (101 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 42 tokens to every session and 319 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…