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/jpantsjoha/ai-native-developer-experience/validategit clone --depth 1 https://github.com/jpantsjoha/ai-native-developer-experienceWhat 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.00154 |
| Opus 5 | $0.00009 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
validate 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
Validate this repository's operating model:
python3 .agents/skills/operating-model-bootstrap/scripts/validate_operating_model.py --target .
- A
seedprofile may PASS with warnings about unresolved project facts — that supports discovery, architecture, ADRs, backlog formation, and R0/R1 work only. - Before R2/R3 work, the profile must be
activewith applicable placeholders resolved; re-run with--require-activeplus the task--checkpointand--evidencepaths. - Report every finding verbatim. A failing validation blocks consequential work; do not route around it.
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 · 14 lines · 18 tokens per session scan A a7b09a2d9b39
validate is a command published in the GitHub repository jpantsjoha/ai-native-developer-experience (11 stars, last pushed 25d ago), licensed Apache-2.0. It adds 18 tokens to every session and 154 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
test-e2e
Write end-to-end tests for critical user journeys.
test-integration
Write integration tests for component boundaries.
iteration-loop
Autonomous full iteration loop for cloud agents — Phase 1 (code-first auto direction lock + compass/plans + Review & Edit chain) through Phase 2–5 (execute → close → PR → merge-ready). Optional args: direction, scale (S|M|L|XL, default M). Not Done until Phase 5 exit checklist passes. Minimal human intervention; no…
newpkg
Generate new package with Nx.
harness-adopt
Apply Harness Starter Kit to the current target repository with the prompt-first adoption workflow.
local-ci-dev
Run local CI to verify changes before completing work.