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/fmflurry/settings-opencode/create-pull-requestgit clone --depth 1 https://github.com/fmflurry/settings-opencodeWhat 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.00021 | $0.00807 |
| Opus 5 | $0.00010 | $0.00404 |
| Sonnet 5 | $0.00004 | $0.00161 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
create-pull-request 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your goal is to create a pull request. Detect the host from origin and use the matching CLI.
0. Detect Host
Run:
git remote get-url origin
Match the URL host:
| Host pattern | CLI to use | Detected as |
|---|---|---|
github.com |
gh |
github |
dev.azure.com, visualstudio.com |
az |
azure |
| anything else | stop | unknown |
If unknown, stop and report: "Origin <url> is not GitHub or Azure DevOps. Cannot create PR."
If the chosen CLI is missing, stop:
- github → "GitHub CLI (
gh) required. Install: https://cli.github.com/" - azure → "Azure CLI (
az) required. Install: https://aka.ms/InstallAzureCli, thenaz extension add --name azure-devops."
Auth check before proceeding:
- github →
gh auth status - azure →
az account show(andaz devops configure --listfor org/project defaults)
1. Inputs
-
Source branch: current branch (
git branch --show-current). -
Target branch: from
$ARGUMENTSif present, else repository default (main,master, or whatever Azure project defines). -
Title: MUST follow conventional commit:
<type>(<scope>): <short summary>Example:
feat(api): add user authentication endpoint -
Body: concise
## Summarysection listing the change set.
2. Push current branch
git push -u origin HEAD
If push fails on divergence, rebase against the target then retry with --force-with-lease (never --force).
3. Create the PR
github
gh pr create \
--base "<target>" \
--title "<conventional-title>" \
--body "<body>"
Add --draft if the user asks for a draft.
azure
Reviewers default to group PIXELS unless the user overrides.
az repos pr create \
--source-branch "<current>" \
--target-branch "<target>" \
--title "<conventional-title>" \
--description "<body>" \
--reviewers "PIXELS" \
--output json
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 · 105 lines · 21 tokens per session scan A 71400d3c2f7c
create-pull-request is a command published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. It adds 21 tokens to every session and 807 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.