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/ribeirogab/zeno-agent/new-issuegit clone --depth 1 https://github.com/ribeirogab/zeno-agentWrote 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/ribeirogab/zeno-agent/new-issue)<a href="https://agentmods.dev/commands/ribeirogab/zeno-agent/new-issue"><img src="https://agentmods.dev/badge/commands/ribeirogab/zeno-agent/new-issue.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00814 |
| Opus 5 | $0.00000 | $0.00407 |
| Sonnet 5 | $0.00000 | $0.00163 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
new-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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New issue
Draft and file a GitHub issue against this repo, following the project's issue-template conventions.
When to invoke
The user (or another agent) types /new-issue from Claude Code. Optional argument: a one-line title or description hint.
Steps
-
Pick the issue type. Ask the user to pick one of:
bug— a reproducible defect.feature— a proposal for a new capability or change.question— a usage or behaviour question.
-
Collect the title. Ask the user for a short, imperative title. Suggest a Conventional Commits prefix matching the type:
bug→fix(scope): ...feature→feat(scope): ...question→question: ...(no Conventional Commits requirement; questions are not changes)
-
Collect the body, mirroring the right template. Use the
.github/ISSUE_TEMPLATE/files literally:bug(template filebug-report.md): description, repro steps, expected, actual, environment, additional context.feature(template filefeature-request.md): description, motivation / use case, alternatives considered, additional context.question(template filequestion.md): question, what you have tried.
-
Roadmap label decision. For
bugandfeatureonly (NOTquestion— questions are not roadmap items), ask the user: "Should this issue be tracked on the public roadmap (ROADMAP.md)?" If yes, the issue gets theroadmaplabel. -
File the issue. Run:
gh issue create \ --title "<title>" \ --label "<bug|enhancement|question>[,roadmap]" \ --body "$(cat <<'EOF' <body assembled from step 3> EOF )"The label list always includes the type label (
bugfor bugs,enhancementfor features,questionfor questions) and conditionallyroadmap.Body line-wrapping (critical). GitHub renders every single
\nin an issue body as<br>(GFM hard-line-break extension, enabled in issue/PR/comment bodies but NOT in repo.mdfiles). Treat each paragraph as ONE line in the heredoc; separate paragraphs with a blank line. Do NOT hard-wrap mid-paragraph at column 72/80 — the wraps become visible breaks in the rendered issue and the body looks fragmented (see incident with #75 / #81 body rendering). Code fences, lists, and tables follow standard Markdown wrapping and are unaffected.
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.
- 4d ago First seen · 58 lines · 0 tokens per session scan A c7b6377685fa
new-issue is a command published in the GitHub repository ribeirogab/zeno-agent (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 814 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
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
session-log
Create or append a session log entry.
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.