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/dgatom/dg-claw/servicenpx skills add DGatoM/DG-Claw --skill servicegit clone --depth 1 https://github.com/DGatoM/DG-ClawWrote 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/dgatom/dg-claw/service)<a href="https://agentmods.dev/skills/dgatom/dg-claw/service"><img src="https://agentmods.dev/badge/skills/dgatom/dg-claw/service.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.00070 | $0.00502 |
| Opus 5 | $0.00035 | $0.00251 |
| Sonnet 5 | $0.00014 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade B, and why
service 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systemctl restart "dgclaw-$SLUG" What it actually says
/dgclaw:service — Controle do servico do assistente
Gerencia o servico systemd dgclaw-<slug> de um assistente DG Claw.
Descobrir os assistentes instalados
systemctl list-units --type=service --all 'dgclaw-*' --no-pager
ls -d "$HOME"/dgclaw/*/ 2>/dev/null
Se houver mais de um, pergunte qual (SLUG). Se houver so um, use ele.
Acoes
Pergunte (ou infira do pedido) o que a pessoa quer e rode:
SLUG=tina # ajuste
# status
systemctl status "dgclaw-$SLUG" --no-pager | head -20
# logs ao vivo (ultimas linhas)
journalctl -u "dgclaw-$SLUG" --no-pager -n 50
# reiniciar (use depois de editar AGENT.md / CLAUDE.md)
sudo systemctl restart "dgclaw-$SLUG"
# desligar / ligar
sudo systemctl stop "dgclaw-$SLUG"
sudo systemctl start "dgclaw-$SLUG"
# desabilitar de vez (nao sobe mais no boot)
sudo systemctl disable --now "dgclaw-$SLUG"
Interpretar problemas comuns
active (running)= no ar.- Reiniciando em loop (
Restart=always) geralmente e: token do Telegram errado,bunfora do PATH, ou workspace inexistente. Chequejournalctle o<workspace>/.dgclaw/config.sh. - "nao responde no Telegram" mas servico ativo: confira o
access.json(o ID da pessoa precisa estar emallowFrom) e se o token bate com o bot certo.
Explique o que achou em linguagem simples e proponha o conserto antes de aplicar.
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 · 54 lines · 70 tokens per session scan B c56e68888696
service is a skill published in the GitHub repository DGatoM/DG-Claw (5 stars, last pushed 14d ago), licensed MIT. It adds 70 tokens to every session and 502 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…