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/initialneil/project-with-reflect/register-apigit clone --depth 1 https://github.com/initialneil/project-with-reflectWhat 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.00020 | $0.00260 |
| Opus 5 | $0.00010 | $0.00130 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
register-api 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
Run the register-api action of the project-with-reflect skill with arguments: $ARGUMENTS
The user can describe the API in plain language — its base URL, docs link, and which env var holds
the key. Extract those from $ARGUMENTS and ask only for what's missing; they don't type positional
args. Creates a connection under $PROJECT_WITH_REFLECT_ROOT/connections/<name>/ (transport http),
installed as a skill /<name>. KEY_ENV_VAR is the name of the env var holding the key (e.g.
SONIOX_API_KEY) — a pointer; the key itself stays in env/keychain, never on disk. docs_url
(e.g. https://soniox.com/docs) is recorded in frontmatter for grounding — the skill fetches it
before coding against the API. After registering, write the endpoints / usage / gotchas into
<name>.md. Follow the skill's steps.
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 · 15 lines · 20 tokens per session scan A d6771f903220
register-api is a command published in the GitHub repository initialneil/project-with-reflect (13 stars, last pushed 13d ago), licensed MIT. It adds 20 tokens to every session and 260 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.