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 commands/abians/code-recall/create-github-issuegit clone --depth 1 https://github.com/AbianS/code-recallWhat 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.00000 | $0.00625 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
create-github-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 yesterday.
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
Create a GitHub issue based on: $ARGUMENTS
Follow these steps:
-
Parse the request
- Analyze the provided description to determine issue type (bug, feature, enhancement, docs, etc.)
- Extract key information: title, description, context, reproduction steps (if bug)
-
Gather context
- If the issue references specific code, search the codebase to understand the current implementation
- Identify relevant files, functions, or components that should be mentioned
- Check for related existing issues using
gh issue list --search "<keywords>"
-
Determine issue labels
- Use
gh label listto see available labels - Select appropriate labels based on issue type:
bug- Something isn't working correctlyenhancement- Improvement to existing functionalityfeature- New functionality requestdocumentation- Documentation improvementsgood first issue- Suitable for new contributorshelp wanted- Extra attention needed
- Use
-
Create the issue with proper formatting Use
gh issue createwith a well-structured body:For bugs:
## Description [Clear description of the bug] ## Steps to Reproduce 1. [Step 1] 2. [Step 2] 3. [Step 3] ## Expected Behavior [What should happen] ## Actual Behavior [What actually happens] ## Environment - OS: [e.g., macOS, Linux] - Version: [relevant version info] ## Additional Context [Screenshots, logs, relevant code references]For features/enhancements:
## Summary [Brief description of the proposed change] ## Motivation [Why is this change needed? What problem does it solve?] ## Proposed Solution [How should this be implemented?] ## Alternatives Considered [Other approaches that were considered] ## Additional Context [Any other relevant information] -
Create the issue
gh issue create \ --title "<descriptive title>" \ --body "<formatted body>" \ --label "<appropriate labels>" -
Confirm creation
- Display the created issue URL
- Show issue number for reference
Example usage:
/create-github-issue Add dark mode support to the dashboard/create-github-issue Bug: Events not being grouped correctly when fingerprint is null/create-github-issue Improve error messages in the ingestion endpoint
Notes:
- Keep titles concise but descriptive (under 72 characters)
- Use imperative mood for feature titles ("Add...", "Fix...", "Update...")
- Include code references using
file:lineformat when relevant - Link to related issues or PRs if applicable
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.
- yesterday First seen · 91 lines · 0 tokens per session scan A 534d1c5cf6fc
create-github-issue is a command published in the GitHub repository AbianS/code-recall (4 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 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-31.
Other commands, from other repositories
refactor-function
Automated function complexity reduction using multi-agent workflow.
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
ng-red-team
Portable command prompt generated from skills/stress-testing-agent-changes/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
milestone-status
PitWay: Show a milestone's status, contract, progress, and tasks.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.