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/iolairus/borderlint/startgit clone --depth 1 https://github.com/iolairus/borderlintWhat 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.00018 | $0.00623 |
| Opus 5 | $0.00009 | $0.00311 |
| Sonnet 5 | $0.00004 | $0.00125 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
start 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.
What it actually says
Single entry point for new work. Figure out which of the three starting situations applies and route the user there. $ARGUMENTS may hint at the topic or a Jira key; use it to preselect answers, never to skip the questions.
Steps
-
Quick state check (fast, no deep inspection):
git branch --show-current, in-flight changes inopenspec/changes/(excludingarchive/), tasks inbacklog/tasks/withstatusother thandone.- If
$ARGUMENTSmatches an existing task or change, or the current branch maps to an in-flight change → this is not new work. Run the/nextlogic instead and stop. - If there is other unrelated in-flight work, mention it in one line ("FYI: PROJ-123 is in progress") but continue — starting something new is allowed.
- If
-
Entry question. Ask with AskUserQuestion: "How does this work start?"
- A. A Jira ticket already exists — the work is already defined in Jira.
- B. No ticket — investigate or propose directly — technical change or exploration; no backlog tracking needed (it can be linked later).
- C. No ticket — create the task first — the work must exist in the backlog/Jira before any spec or code.
-
Route by answer. The user's selection counts as asking to proceed, so run the routed command's logic directly:
- A → ask for the Jira key (e.g.
PROJ-123) if not in$ARGUMENTS, then run/task-import <key>. - B → ask one follow-up with AskUserQuestion: does the user already know what to change?
- Yes, the change is clear →
/opsx:propose <name>(ask for a short kebab-case change name). - No, needs investigation first →
/opsx:explore, reminding that it ends by suggesting/opsx:propose.
- Yes, the change is clear →
- C → ask one follow-up with AskUserQuestion: initiative or single task?
- Initiative (several tasks, requirements unclear) →
/req-capture <topic>, then/task-generate. - Single task (one verifiable outcome, scope clear) →
/task-new <title>.
- Initiative (several tasks, requirements unclear) →
- A → ask for the Jira key (e.g.
-
Never skip the gates downstream. Whatever the route, the golden rule holds: no code until an OpenSpec change exists, is reviewed, and the branch gate is resolved.
/startonly chooses the on-ramp.
Output format: after routing, one line stating the situation chosen and the command now running. If the user aborts the questions, list the three routes with their commands so they can invoke one manually.
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 · 31 lines · 18 tokens per session scan A f197f59fde1a
start is a command published in the GitHub repository iolairus/borderlint (7 stars, last pushed 9d ago), licensed MIT. It adds 18 tokens to every session and 623 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
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.