github-ops

A command for running the project's defined GitHub backlog workflow. GitHub is a service for hosting code, tracking issues, and managing development work.

In plain words
What is it for?
Use it for GitHub issue triage and backlog management, following the workflow defined in the project's internal agent file.
Why use it?
It applies the repository's canonical rules for sorting, routing, and managing backlog items instead of relying on ad hoc decisions.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/jnpiyush/agentx/github-ops
Clone the repo
git clone --depth 1 https://github.com/jnPiyush/AgentX

Made for: Claude Code.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 73 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00073
Opus 5 $0.00012 $0.00036
Sonnet 5 $0.00005 $0.00015
Haiku 4.5 $0.00002 $0.00007

Measured 2d ago against content hash fe8de88e4fa1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-ops 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 2d 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.

.claude/commands/github-ops.md · 7 lines

What it actually says

Read .github/agents/internal/github-ops.agent.md before taking action.

Treat this command as a thin wrapper over the canonical agent file. Use that file for GitHub triage, routing, and backlog-management rules.

Changes

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.

  1. 2d ago First seen · 7 lines · 23 tokens per session scan A fe8de88e4fa1

Subscribe to this mod's changes

github-ops is a command published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 73 once invoked, about $0.0001 per session on Opus 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.