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 eobarretooo/ClawLite --skill github-issuesgit clone --depth 1 https://github.com/eobarretooo/ClawLiteWrote 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/eobarretooo/clawlite/github-issues)<a href="https://agentmods.dev/skills/eobarretooo/clawlite/github-issues"><img src="https://agentmods.dev/badge/skills/eobarretooo/clawlite/github-issues/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/eobarretooo/clawlite/github-issues"><img src="https://agentmods.dev/badge/skills/eobarretooo/clawlite/github-issues.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00401 |
| Opus 5.5 | $0.00011 | $0.00160 |
| Sonnet 5.5 | $0.00005 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
github-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 1mo 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
GitHub Issues
Use this skill for GitHub issue and PR management using the gh CLI.
Auth
gh auth status # verify active session
gh auth login # interactive login
# or set GH_TOKEN env var for headless operation
Issues
gh issue list --repo owner/repo --state open --limit 20
gh issue list --repo owner/repo --label bug --assignee @me
gh issue view 123 --repo owner/repo
gh issue create --repo owner/repo --title "Title" --body "Body" --label bug
gh issue close 123 --repo owner/repo
gh issue comment 123 --repo owner/repo --body "comment text"
gh issue edit 123 --repo owner/repo --add-label "priority:high"
Pull Requests
gh pr list --repo owner/repo --state open
gh pr view 456 --repo owner/repo
gh pr create --title "Fix bug" --body "Fixes #123" --base main
gh pr merge 456 --squash --repo owner/repo
gh pr review 456 --approve --body "LGTM"
Search
gh issue list --search "is:issue is:open label:bug" --repo owner/repo
gh pr list --search "is:pr is:open review-requested:@me"
Safety notes
- Require explicit approval before closing or merging.
- Never force-push or rewrite history without explicit user instruction.
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.
- 1mo ago First seen · 53 lines · 27 tokens per session scan A c2776228797d
github-issues is a skill published in the GitHub repository eobarretooo/ClawLite (50 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 401 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-08-30.
Other skills, from other repositories
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
bt6-queue-audit
Audit the full pull-request and issue queue of a BT6 research or support repository, classifying readiness, evidence risk, and next action without mutating tracker state.