grepai is a local command-line tool that searches source code by meaning and traces function call graphs, rather than matching only exact words. Developers and coding agents use it to find relevant code, understand relationships between functions, and provide focused context for changes while keeping the code on the local machine. The catalogue entries expose its commands, skills, agent, and instruction for coding-agent workflows.
Borrowing it
Nothing to install: this file belongs to yoanbernabeu/grepai. 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/yoanbernabeu/grepai/main/.claude/commands/work-issue.mdgit clone --depth 1 https://github.com/yoanbernabeu/grepaiWrote 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/yoanbernabeu/grepai/work-issue)<a href="https://agentmods.dev/commands/yoanbernabeu/grepai/work-issue"><img src="https://agentmods.dev/badge/commands/yoanbernabeu/grepai/work-issue/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/yoanbernabeu/grepai/work-issue"><img src="https://agentmods.dev/badge/commands/yoanbernabeu/grepai/work-issue.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.01870 |
| Opus 5.5 | $0.00000 | $0.00748 |
| Sonnet 5.5 | $0.00000 | $0.00374 |
| Haiku 4.5 | $0.00000 | $0.00187 |
Grade A, and why
work-issue 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 today.
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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Issue Command
You are an issue implementation assistant. Follow these steps carefully to implement a GitHub issue from start to finish. Always ask for user confirmation before critical operations.
Step 1: Retrieve Issue Information
Use gh issue view $ARGUMENTS --json number,title,body,state,labels,assignees to get issue details.
If no argument is provided, list open issues with gh issue list and ask the user which one to work on.
Display a clear summary of:
- Issue number and title
- Description/requirements
- Labels and priority
Step 2: Enter Plan Mode
CRITICAL: Enter plan mode using the EnterPlanMode tool before any implementation.
In plan mode:
- Analyze the issue requirements thoroughly
- Explore the codebase using grepai search to understand related code
- Identify files that need modification or creation
- Design the implementation approach
- Break down into clear, actionable steps
- Consider edge cases and potential issues
- Plan necessary tests
Write your plan and exit plan mode with ExitPlanMode when ready for user approval.
Step 3: Create Feature Branch
After plan approval:
-
Ensure you're on main and up-to-date:
git checkout main git pull origin main -
Create a feature branch following the convention:
git checkout -b <type>/<issue-number>-<short-description>Types:
feat,fix,docs,refactor,test,chore -
Confirm branch creation to the user
Step 4: Implement Changes
Follow your approved plan step by step:
- Use TodoWrite to track implementation progress
- Make focused, incremental changes
- Follow project coding conventions and the V1 Stability Rules (see AGENTS.md)
- Add/update tests as needed
- Mark todos as completed as you progress
After each significant change, briefly summarize what was done.
Step 5: Test the Implementation Locally
CRITICAL: You must build the CLI and test it on the actual codebase, not just run unit tests.
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.
- today Changed · +7 lines 1b92a756c467
- 1mo ago First seen · 295 lines · 0 tokens per session scan A 59b7a17ec04b
work-issue is a command published in the GitHub repository yoanbernabeu/grepai (1,925 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,870 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
taskstoissues
A command that turns structured tasks from project design documents into ordered GitHub Issues, written in simplified Chinese.
next
Suggest the most likely next workflow action based on current context.
afs
Start feature [agents...] - create workspace and begin implementation (shortcut for feature-start).
aft
Transfer feature from its current agent to a different agent — preserves commits and in-flight work (shortcut for feature-transfer).
aigon-feature-transfer
Hand a stuck or paywalled in-progress feature from its current agent to a different agent, without losing commits or in-flight work. Intended for.
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).