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 terrylica/cc-skills --skill gogit clone --depth 1 https://github.com/terrylica/cc-skillsWrote 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/terrylica/cc-skills/go)<a href="https://agentmods.dev/skills/terrylica/cc-skills/go"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/go/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/terrylica/cc-skills/go"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/go.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 8 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- medium Rogue Agent · line 16 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 30 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00031 | $0.03130 |
| Opus 5.5 | $0.00012 | $0.01252 |
| Sonnet 5.5 | $0.00006 | $0.00626 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
go 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 26d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⛔ ITP Workflow — STOP AND READ
DO NOT ACT ON ASSUMPTIONS. Read this file first.
This is a structured workflow command. Follow the phases in order.
Your FIRST and ONLY action right now: Execute the TodoWrite below.
Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.
⛔ MANDATORY FIRST ACTION: Plan-Aware Todo Integration
YOUR FIRST ACTION MUST BE a MERGED TodoWrite that preserves existing todos.
DO NOT:
- ❌ Overwrite existing todos from plan files or previous sessions
- ❌ Ignore the plan file at
~/.claude/plans/*.md - ❌ Create your own todos without checking for existing ones
- ❌ Jump to coding without completing Step 0
- ❌ Create a branch before TodoWrite
Follow the full merge strategy (Steps 0.1-0.5) and TodoWrite template: Todo Merge Strategy
After TodoWrite completes, proceed to Preflight section below.
Quick Reference
Skills Invoked
| Skill | Phase | Purpose |
|---|---|---|
implement-plan-preflight |
Preflight | ADR + Design Spec creation |
impl-standards |
Phase 1 | Error handling, constants |
adr-code-traceability |
Phase 1 | Code-to-ADR references |
code-hardcode-audit |
Phase 1 | Pre-release validation |
semantic-release |
Phase 3 | Version tagging + release |
pypi-doppler |
Phase 3 | PyPI publishing (if applicable) |
File Locations
| Artifact | Path | Notes |
|---|---|---|
| ADR | /docs/adr/$ADR_ID.md |
Permanent |
| Design Spec | /docs/design/$ADR_ID/spec.md |
Permanent, SSoT after Preflight |
| Global Plan | ~/.claude/plans/<adj-verb-noun>.md |
EPHEMERAL - replaced on new plan |
What ships with it
8 files 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.
- references/arguments-reference.md 2.8 KB
- references/evolution-log.md 683 B
- references/phase1-protocols.md 3.1 KB
- references/phase2-scripts.md 1.3 KB
- references/phase3-gate-logic.md 3.9 KB
- references/preflight-checkpoint.md 1.3 KB
- references/todo-merge-strategy.md 3.6 KB
- references/workflow-preview.md 1.7 KB
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.
- 26d ago Changed cc4a1e584112
- 1mo ago Changed · -4 lines 6bb22f8a1f8c
- 1mo ago First seen · 317 lines · 31 tokens per session scan A f998e7bf7a58
go is a skill published in the GitHub repository terrylica/cc-skills (1 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 3,130 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
low-code-platforms
Low-code and internal tool platforms including Retool, Supabase, Appsmith, Tooljet, n8n, and Zapier. Use when building admin panels, internal tools, workflow automations, or integrating low-code platforms with custom code.
host-ssh
Run PowerShell on Windows hosts or a POSIX shell on macOS/Linux hosts over SSH, via the machine registry in the guide Environment (GASSHMACHINES). Use when the user needs host OS tasks — drives, dotnet, Playwright, processes, SSH into their laptop or desktop — not file I/O on paths already visible in the workspace…
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
social-media-strategy
Platform-specific tactics, content optimization, audience growth, and analytics-driven social media strategy. Use when planning a social strategy, optimizing posts for a specific platform, or growing and measuring an audience.
agentic-orchestration
Patterns for multi-agent coordination, task decomposition, handoffs, and workflow orchestration. Best practices for building and managing agent systems. Use when designing how multiple agents coordinate — splitting up tasks, defining handoffs, or choosing an orchestration topology.
book-publishing
Multi-book content, voice, and production workflows for nonfiction authoring. Use when planning a book, maintaining consistent voice across chapters, structuring a manuscript, or running an end-to-end publishing pipeline.