Borrowing it
Nothing to install: this file belongs to cognitx-leyton/codegraph. 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/cognitx-leyton/codegraph/main/.claude/commands/file-issues.mdgit clone --depth 1 https://github.com/cognitx-leyton/codegraphWrote 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/cognitx-leyton/codegraph/file-issues)<a href="https://agentmods.dev/commands/cognitx-leyton/codegraph/file-issues"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/file-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/cognitx-leyton/codegraph/file-issues"><img src="https://agentmods.dev/badge/commands/cognitx-leyton/codegraph/file-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.00011 | $0.00406 |
| Opus 5.5 | $0.00004 | $0.00162 |
| Sonnet 5.5 | $0.00002 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
file-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 2mo 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
File Issues (Step 11)
During implementation, you may discover:
- Enhancement ideas that are out of scope for the current work
- Bugs in unrelated code
- Missing features that would be nice to have
- Technical debt worth tracking
Do NOT implement these. File them as GitHub issues so they're tracked for future work.
Process
1. Review discoveries
Look through:
- Deviations noted during
/implement - Suggestions from
/review-prthat were out of scope - Ideas surfaced during
/critique - Errors seen during
/testthat aren't blockers
2. For each discovery, create an issue
gh issue create --title "<type>: <concise title>" --body "$(cat <<'EOF'
## Context
Discovered during implementation of <current work>.
## Description
<What the issue is, with specifics>
## Suggested approach
<Brief idea of how to address it, if known>
## References
- Related file(s): `<path>`
- Related commit: `<sha>`
- Surfaced by: `/review-pr` | `/critique` | `/test`
EOF
)" --label "<enhancement|bug|tech-debt>"
3. Report
Issues Filed
-------------
- #N: <title> (enhancement)
- #N: <title> (bug)
- #N: <title> (tech-debt)
These are tracked for future work — not part of the current release.
Ready for: /create-pr
Labels
| Label | When to use |
|---|---|
enhancement |
New feature or capability |
bug |
Something broken in existing code |
tech-debt |
Refactoring, cleanup, performance |
documentation |
Missing or outdated docs |
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.
- 2mo ago First seen · 73 lines · 11 tokens per session scan A d63aca1ed35f
file-issues is a command published in the GitHub repository cognitx-leyton/codegraph (12 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 406 once invoked, about $0.0000 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 commands, from other repositories
feedback
A design-stage security review for product requirement documents and other planning documents; a PRD is a document describing what a product should do.
va
A read-only security review of a codebase across eight architecture areas, with findings checked against file-and-line evidence.
compliance
A follow-up security check that verifies whether earlier findings were fixed and, depending on the selected mode, looks for new problems.
pentest
A read-only penetration-testing command for examining source code from an attacker’s perspective and producing proof-of-concept checks. Penetration testing is authorized security testing that tries to verify exploitable weaknesses.
run
A security-workflow coordinator that turns a natural-language request into a plan involving code review, verification, attack testing, or reporting.
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.