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/allgpt-co/quickvoice/git-integrationnpx skills add allgpt-co/QuickVoice --skill git-integrationgit clone --depth 1 https://github.com/allgpt-co/QuickVoiceWhat 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.00015 | $0.00159 |
| Opus 5 | $0.00008 | $0.00079 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
gsd:reference:git-integration 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.
What it actually says
GSD Git Integration Reference
Guide for using Git with GSD workflow.
Commit Patterns
- Atomic commits per task
- Descriptive commit messages
- Link to task when possible
- Regular commits during work
Branch Strategy
- Feature branches for tasks
- Main branch for stable
- Checkpoints as tags
Best Practices
- Commit early and often
- Write meaningful messages
- Review before pushing
- Keep commits focused
Success Criteria
Clean git history with traceable changes.
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 · 36 lines · 15 tokens per session scan A 367271b15ee5
gsd:reference:git-integration is a skill published in the GitHub repository allgpt-co/QuickVoice (491 stars, last pushed 21d ago), licensed MIT. It adds 15 tokens to every session and 159 once invoked, about $0.0001 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
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
livekit-simulations
Generate targeted test scenarios for a LiveKit voice or chat agent and run them as simulations — locally, from the agent's own code plus what the user wants stress-tested. Use whenever the user wants to "test my agent", "what should I test", "create/generate simulation scenarios", "make a sim test suite", "use lk…
webhook-handler-patterns
Best practices for webhook handlers: verify → parse → handle idempotently. Covers idempotency, error handling, retry logic, framework-specific gotchas (Express, Next.js, FastAPI). Use when implementing any webhook receiver.
80-livekit-agents-panaversity-agentfactory-1f8ecf89
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
80-livekit-agents-majiayu000-claude-skill-registr
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.
80-livekit-agents-panaversity-agentfactory-1f8ecf89
Create your LiveKit Agents skill from official documentation, then learn to improve it throughout the chapter.