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/eobarretooo/clawlite/gh-issuesnpx skills add eobarretooo/ClawLite --skill gh-issuesgit clone --depth 1 https://github.com/eobarretooo/ClawLiteWhat 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.00031 | $0.00368 |
| Opus 5 | $0.00015 | $0.00184 |
| Sonnet 5 | $0.00006 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
gh-issues 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
gh-issues
Command-bound skill for GitHub issue operations through gh issue ....
Auth expectations
- Primary path: authenticated
ghCLI session (gh auth status). - Optional path:
GH_TOKENin environment for headless/auth bootstrap flows. - If auth fails, stop early and fix credentials before spawning implementation sessions.
Quick usage
gh issue list --repo owner/repo --state open --limit 20
gh issue view 123 --repo owner/repo
gh issue comment 123 --repo owner/repo --body "Working on this"
Orchestration workflow (issue -> fix -> PR)
- Discover and prioritize issues with
gh issue listfilters (--label,--assignee,--search). - Spawn workers via
sessions_spawn/subagents(one issue per worker, explicit branch naming and test expectations). - Track worker progress with
session_status; inspect outcomes withsessions_history. - Validate edits/tests locally via
process, apply final deltas withapply_patchwhen needed. - Open or update PRs with
gh pr createand post issue linkage (Fixes #<n>).
Safety notes
- Require explicit approval for destructive git actions (force push, history rewrite, branch deletion).
- Keep edits scoped to each issue branch; avoid mixing unrelated fixes.
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 · 39 lines · 31 tokens per session scan A d11c9876b1ff
gh-issues is a skill published in the GitHub repository eobarretooo/ClawLite (49 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 368 once invoked, about $0.0002 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
a0-create-agent
Create a new Agent Zero agent profile (subordinate). Covers where profiles live (user / plugin-distributed / project-scoped), the agent.yaml schema, the prompt inheritance & override model, and optional profile-specific tools and extensions. Use for any "create/add/new agent profile" request.
a0-create-plugin
Create, extend, or modify Agent Zero plugins. Follows strict full-stack conventions (usr/plugins, plugin.yaml, Store Gating, AgentContext, plugin settings). Use for UI hooks, API handlers, lifecycle extensions, or plugin settings UI.
linux-desktop
Use only for Agent Zero's built-in Docker/Xpra Linux Desktop, XFCE apps, LibreOffice GUI apps, file manager, terminal, or visual workflows inside the Agent Zero runtime. Not for A0 CLI /computer-use or computeruseremote host control.
a0-contribute-plugin
Guide for publishing an Agent Zero plugin to the community Plugin Index (a0-plugins repo). Covers GitHub repo setup, index.yaml creation, CI validation rules, and PR submission. Use when the user wants to share, publish, submit, or contribute a plugin to the Plugin Hub so other Agent Zero users can find and install it.
a0-review-plugin
Full audit of Agent Zero plugins in usr/plugins/. Reviews manifest validity, directory structure, code patterns (Store Gating, notifications, imports), security, and duplicate detection against the community index. Use when asked to review, audit, validate, or check an existing plugin before using or contributing it.
host-computer-use-linux
Backend-specific Linux guidance for computeruseremote. Load after status or startsession reports backendfamily linux, backendid wayland, or AT-SPI features. Covers AT-SPI structural targeting, Wayland portal caveats, and screenshot verification.