Borrowing it
Nothing to install: this file belongs to llama-farm/llamafarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/llama-farm/llamafarm/main/.agents/commands/github_issues.mdgit clone --depth 1 https://github.com/llama-farm/llamafarmWrote 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/commands/llama-farm/llamafarm/github_issues)<a href="https://agentmods.dev/commands/llama-farm/llamafarm/github_issues"><img src="https://agentmods.dev/badge/commands/llama-farm/llamafarm/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/commands/llama-farm/llamafarm/github_issues"><img src="https://agentmods.dev/badge/commands/llama-farm/llamafarm/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.00000 | $0.02940 |
| Opus 5.5 | $0.00000 | $0.01176 |
| Sonnet 5.5 | $0.00000 | $0.00588 |
| Haiku 4.5 | $0.00000 | $0.00294 |
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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub - Issue Management
You are tasked with managing GitHub issues, including creating issues from thoughts documents, updating existing issues, and following the team's specific workflow patterns.
Initial Setup
First, verify that GitHub MCP tools are available by checking if any mcp__GitHub__ tools exist. If not, attempt to use the GitHub API directly or VSCode extension instead.
If tools are available, respond based on the user's request:
For general requests:
I can help you with GitHub issues. What would you like to do?
1. Create a new issue from a thoughts document
2. Create a new issue ad-hoc
3. Add a comment to an issue (I'll use our conversation context)
4. Search for issues
5. Update issue status or details
For specific create requests:
I'll help you create a GitHub issue from your thoughts document. Please provide:
1. The path to the thoughts document (or topic to search for) -or- a good description of the issue to create.
2. Any specific focus or angle for the issue (optional)
Then wait for the user's input.
Team Workflow & Status Progression
The team follows a specific workflow to ensure alignment before code implementation:
- New → All new issues start here for initial review
- Researching → Active research/investigation underway
- Planning → Actively writing the implementation plan
- Implementing → Active development and review
- Done → Completed
Key principle: Review and alignment happen at the planning stage (not PR stage) to move faster and avoid rework.
Important Conventions
URL Mapping for Thoughts Documents
When referencing thoughts documents, always provide GitHub links using the links parameter:
thoughts/shared/...→https://github.com/llama-farm/thoughts/blob/main/repos/llamafarm/shared/...thoughts/alice/...→https://github.com/llama-farm/thoughts/blob/main/repos/llamafarm/alice/...thoughts/global/...→https://github.com/llama-farm/thoughts/blob/main/global/...
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 · 334 lines · 0 tokens per session scan A 538c08136b3c
github_issues is a command published in the GitHub repository llama-farm/llamafarm (836 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,940 tokens. 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 commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.