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/bjcoombs/ai-native-toolkit/issuesgit clone --depth 1 https://github.com/bjcoombs/ai-native-toolkitWhat 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.00023 | $0.01626 |
| Opus 5 | $0.00012 | $0.00813 |
| Sonnet 5 | $0.00005 | $0.00325 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
issues 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Marathon
Thin orchestrator. Triages open issues, then delegates execution of
agent-readyissues to the marathon skill (same engine as/tm).
Configuration
Read the repo's CLAUDE.md ## Marathon Configuration (GitHub Issues subsection) for label
names, with defaults:
- Agent-ready label:
agent-ready - Needs-triage label:
needs-triage - In-progress label:
in-progress - Issue exclude labels: (none)
Also read base branch, required approvals, and bot-reviewer rules (shared with /tm).
Phase 0: Capability Detection
echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS # set $TEAMS_AVAILABLE (true if "1")
Routing
ORG=$(gh repo view --json owner --jq '.owner.login')
REPO=$(gh repo view --json name --jq '.name')
# Optional scope filter from $ARGUMENTS — narrows the issue universe; routing still applies within it.
SCOPE_LABEL="$ARGUMENTS" # empty = all open issues
FILTER=(); [ -n "$SCOPE_LABEL" ] && FILTER=(--label "$SCOPE_LABEL")
READY=$(gh issue list --label "agent-ready" "${FILTER[@]}" --state open --json number --jq 'length')
READY > 0→ Marathon mode. Work ONLY theagent-readyissues. Do NOT assess or modify untagged issues — the human has curated the queue by tagging.READY == 0→ Triage mode (below).
Triage Mode (no agent-ready issues exist)
Enumerate open issues minus the exclude labels:
gh issue list "${FILTER[@]}" --state open --json number,title,body,labels | \
jq '[.[] | select((.labels[].name) as $l | ($l | IN("<exclude-labels>")) | not)]'
If $ARGUMENTS (a scope label) was given, only issues carrying it are considered; routing still applies within that subset.
For each issue, assess whether it is actionable as-is (clear scope, acceptance criteria inferable, no open question):
- Clear enough → add the agent-ready label:
gh issue edit <N> --add-label "agent-ready" - Ambiguous → post clarifying questions as a comment, then label needs-triage:
gh issue comment <N> --body "$(cat <<'EOF' Triage questions before this can be picked up by an agent: 1. <question> 2. <question> EOF )" gh issue edit <N> --add-label "needs-triage"
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.
- 2d ago First seen · 150 lines · 23 tokens per session scan A 2096e1de65ae
issues is a command published in the GitHub repository bjcoombs/ai-native-toolkit (30 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,626 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
README
Git workflow and quality assurance commands for the claude-skills repository.
agentlas-cloud
Staff a task only from the signed-in owner's Agent Cloud agents.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
tldr
Re-apply TLDR rules for this turn (verdict first, no filler).
execute
Interactive workflow for workspace isolation, pane-delegated implementation, testing, review, and cleanup.