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 tethergit 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/tether)<a href="https://agentmods.dev/skills/terrylica/cc-skills/tether"><img src="https://agentmods.dev/badge/skills/terrylica/cc-skills/tether.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.1 | $0.00034 | $0.00701 |
| Opus 5 | $0.00017 | $0.00351 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade B, and why
tether scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **Status**: Read current ~/.claude/settings.json How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/asciinema-tools:tether
Manage Claude Code hooks for asciinema-tools automation.
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.
Arguments
| Argument | Description |
|---|---|
install |
Add hooks to settings.json |
uninstall |
Remove asciinema-tools hooks |
status |
Show current hook configuration |
--backup-on-stop |
Auto-backup when session ends |
--convert-on-stop |
Auto-convert on session end |
-y, --yes |
Skip confirmation prompts |
Hook Definitions
PostToolUse Hook (backup-on-stop)
{
"hooks": {
"PostToolUse": [
{
"matcher": "Bash",
"command": "asciinema-backup-if-active"
}
]
}
}
Execution
Skip Logic
- If action provided -> execute directly
- If hook type flags provided -> use specific hooks
Workflow
- Status: Read current ~/.claude/settings.json
- Action: AskUserQuestion for action type
- Hooks: AskUserQuestion for hook selection
- Execute: Modify settings.json
- Verify: Confirm changes applied
Examples
# Check current hook status
/asciinema-tools:tether status
# Install auto-backup hook
/asciinema-tools:tether install --backup-on-stop
# Install without prompts
/asciinema-tools:tether install -y
# Remove all asciinema hooks
/asciinema-tools:tether uninstall
Troubleshooting
| Issue | Cause | Solution |
|---|---|---|
| jq not found | jq not installed | brew install jq |
| Settings file not found | ~/.claude/ doesn't exist | Create with mkdir -p ~/.claude |
| Hooks not working | Session not restarted | Restart Claude Code session |
| Backup not triggering | No active recordings | Start recording first with daemon |
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.
- 7d ago First seen · 92 lines · 34 tokens per session scan B c79878a7802d
tether is a skill published in the GitHub repository terrylica/cc-skills (62 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 701 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
customer-persona-builder
Data-driven customer persona development combining market research, user behavior analysis, and segmentation frameworks. Use when creating buyer personas, ideal customer profiles (ICPs), or user archetypes.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.
generic-code-reviewer
Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.