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/c0ntr0lledcha0s/claude-code-plugin-automations/issue-creategit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/issue-create)<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-create"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/issue-create.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.00017 | $0.01874 |
| Opus 5 | $0.00009 | $0.00937 |
| Sonnet 5 | $0.00003 | $0.00375 |
| Haiku 4.5 | $0.00002 | $0.00187 |
Grade A, and why
issue-create 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Issue
Create a new GitHub issue following project conventions with all metadata properly configured.
Usage
/issue-create "Add validation for hook matchers"
/issue-create # Interactive mode
Arguments
- First argument (optional): Issue title. If omitted, prompts for title.
What This Does
Creates an issue with all factors properly configured:
- Title - Validates naming conventions (no type prefixes)
- Labels - Applies type, priority, scope, and branch labels
- Milestone - Optionally assigns to milestone
- Relationships - Links to parent, blocking, or related issues
- Project - Adds to project board with initial status
- Body - Includes structured template with acceptance criteria
Workflow
Step 0: Load Environment and Detect Scope
Before any prompts, load the environment and attempt scope detection:
# Load environment
ENV_FILE=".claude/github-workflows/env.json"
if [[ -f "$ENV_FILE" ]]; then
DETECTED_SCOPE=$(jq -r '.branch.scopeLabel // empty' "$ENV_FILE")
SUGGESTED_SCOPES=$(jq -r '.labels.suggestedScopes[]? // empty' "$ENV_FILE")
fi
# If no scope from env, try branch name
if [[ -z "$DETECTED_SCOPE" ]]; then
BRANCH=$(git rev-parse --abbrev-ref HEAD 2>/dev/null)
# Match branch against suggested scopes
for scope in $SUGGESTED_SCOPES; do
if [[ "${BRANCH,,}" == *"${scope,,}"* ]]; then
DETECTED_SCOPE="scope:$scope"
break
fi
done
fi
Step 1: Title Validation
Check title follows conventions:
- No type prefixes like
[BUG],[FEATURE],[ENHANCEMENT] - Descriptive and actionable
- 50-72 characters recommended
❌ "[BUG] Login fails" → Suggest: "Fix login authentication failure"
❌ "[FEATURE] Add auth" → Suggest: "Add user authentication"
✅ "Add validation for hook matchers"
Step 2: Label Selection
Prompt for each label dimension:
Type (required):
Select issue type:
1. bug - Something isn't working
2. feature - New functionality
3. enhancement - Improve existing feature
4. documentation - Documentation changes
5. refactor - Code improvement
6. chore - Maintenance task
Your choice: _
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 · 338 lines · 17 tokens per session scan A 69fa5e5c6e85
issue-create is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 1,874 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-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.