Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add sjungling/sjungling-claude-plugins/plugin install workflowWrote 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/sjungling/sjungling-claude-plugins/create-issue)<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/create-issue"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/create-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.1 | $0.00018 | $0.01182 |
| Opus 5 | $0.00009 | $0.00591 |
| Sonnet 5 | $0.00004 | $0.00236 |
| Haiku 4.5 | $0.00002 | $0.00118 |
Grade A, and why
create-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 6d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a GitHub issue using the best available content from the current session.
Parse $ARGUMENTS for an optional file path override.
Step 1: Discover Content
Run the discovery script to find the best content source. The script is located relative to this command file:
SCRIPT_DIR="$(cd "$(dirname "$0")/../scripts" 2>/dev/null && pwd || echo "")"
If $SCRIPT_DIR is empty or the script does not exist, compute the path from the plugin root. The script lives at plugins/workflow/scripts/discover-issue-content.sh relative to the marketplace root. As a fallback, use ${CLAUDE_PLUGIN_ROOT}/scripts/discover-issue-content.sh if that variable is available.
Run the script, passing $ARGUMENTS if non-empty:
DISCOVERY=$(bash "$SCRIPT_DIR/discover-issue-content.sh" $ARGUMENTS 2>&1)
If the script exits non-zero, check stderr for {"error": "..."} and report the error to the user. Common errors:
gh CLI not installed— tell user to install GitHub CLIjq not installed— tell user to install jqnot in a git repository— abortfile not found: <path>— abort with the missing file path
Parse the JSON output:
SOURCE=$(echo "$DISCOVERY" | jq -r '.source')
PRIMARY=$(echo "$DISCOVERY" | jq -r '.primary')
SECONDARY=$(echo "$DISCOVERY" | jq -r '.secondary')
LABEL=$(echo "$DISCOVERY" | jq -r '.label')
REPO=$(echo "$DISCOVERY" | jq -r '.repo')
SPECS=$(echo "$DISCOVERY" | jq -r '.candidates.specs[]' 2>/dev/null)
PLANS=$(echo "$DISCOVERY" | jq -r '.candidates.plans[]' 2>/dev/null)
Step 2: Resolve Content
Based on the SOURCE value:
explicit or claude-plan
PRIMARY already points to the file. Use it directly as $BODY_FILE.
superpowers
If PRIMARY is non-empty, use it as $BODY_FILE.
If PRIMARY is empty, there are multiple candidates that need disambiguation. Use AskUserQuestion to present the candidates from SPECS and/or PLANS and ask which file to use as the issue body. Set $BODY_FILE to the chosen file.
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.
- 6d ago First seen · 133 lines · 18 tokens per session scan A 5bc67ed0359f
create-issue is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 23d ago), licensed MIT. It adds 18 tokens to every session and 1,182 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.