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/sauravvarma/garage/code-agentnpx skills add sauravvarma/garage --skill code-agentgit clone --depth 1 https://github.com/sauravvarma/garageWhat 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.00113 | $0.05987 |
| Opus 5 | $0.00056 | $0.02993 |
| Sonnet 5 | $0.00023 | $0.01197 |
| Haiku 4.5 | $0.00011 | $0.00599 |
Grade A, and why
code-agent 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 2d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
code-agent — coding specialist
Spec preflight
Before doing the work, verify the artifacts this skill depends on. Stop and present a checklist if anything required is missing — do not silently proceed with assumptions.
Required:
CLAUDE.md— project context, commands, preflight sectiondocs/REPO-CONVENTIONS.md— architectural patterns (data flow, routing, state, code splitting, analytics, styling)docs/COMPONENT-SPECS.md— code component index and shared atoms
Recommended (for the feature in scope):
docs/[FEATURE]-IDEAS.md— decision table with locked decisions, route chrome, design rationale
Optional:
.claude/rules/— project-specific gates
If anything required is missing, tell the user exactly which docs are missing and offer two paths:
- (default) "Run
/spec-first-project-setupto scaffold the missing pieces, then come back." - "Proceed without — I'll make assumptions and flag them as I go."
If [FEATURE]-IDEAS.md exists but has any decision in the table with status open for the feature in scope, refuse to implement until those decisions are locked. Route the user using the lock-state hierarchy:
- If
docs/DESIGN-HEURISTICS.mdis missing (or any open decision row hasType: direction) → direction itself isn't locked. Say: "Decisions [N], [M] are still open and direction-level. Run/design-explore '[feature intent]'to discover and lock the direction first." - If
docs/DESIGN-HEURISTICS.mdis present and open decisions are allType: variant(or untyped, in which case assume variant once direction is locked) → variant choices within a locked direction. Say: "Decisions [N], [M] are still open within the locked direction. Run/design-agent '[feature intent]'to generate variants and let the user pick."
(Same lock-state hierarchy as /design-agent's spec preflight — keep both in sync if changing.)
To match the user's task to its [FEATURE]-IDEAS.md, use the closest filename match. If ambiguous or none, ask the user which feature doc applies.
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.
- 2d ago First seen · 222 lines · 113 tokens per session scan A 68cbfd176790
code-agent is a skill published in the GitHub repository sauravvarma/garage (3 stars, last pushed 1mo ago), licensed MIT. It adds 113 tokens to every session and 5,987 once invoked, about $0.0006 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-31.
Other skills, from other repositories
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…
lingtai-tui-help
Anything you need to know about LingTai TUI. Read this first for the stable mental model, major-feature map, interface and slash-command help, or the correct source/manual route for a TUI question. It stays thin: exact command prose lives in the localized help assets, precise Go structure lives in lingtai-tui-anatomy…
omd:autopilot
One-prompt autonomous product design and implementation. Use automatically for broad greenfield UI requests such as 'from scratch', '새 제품/화면을 알아서 만들어줘', or requests that delegate DESIGN.md creation. It decides whether to reuse, establish, refresh, or skip a project design system; asks at most one consequential…
omd:learn
.omd/preferences.md의 status:pending 항목을 Core v2 System Graph에 합쳐 DESIGN.md를 재생성하고 status를 applied로 플립. '프리퍼런스 정리해줘', 'fold preferences', 'apply all corrections', 「好みをDESIGN.mdに反映」, 「套用偏好」류의 요청에 트리거. 단발성 교정 기록은 omd:remember.
omd:codex-image
이미지 placeholder를 동적으로 materialize. Codex 채널에서는 내장 image-generation primitive 호출, Claude Code 채널에서는 omd-asset-curator로 fall back, OpenCode에서는 spec dump. HTML/MD의 블록을 단일 source of truth로 사용. '이미지 생성해줘', '플레이스홀더 채워줘', '코덱스로 이미지 만들어' 류 트리거.
omd:orchestrator
멀티 에이전트 디자인 워크플로우 supervisor. writer, locale adaptation, humanize, UI slop audit, designer review, final QA, image materialization을 routing한다. 2-round revision cap을 유지하며 다국어 문서·UI 개선·출간 준비처럼 여러 역할이 필요한 요청에 사용한다.