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/yonatangross/orchestkit/assessgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/yonatangross/orchestkit/assess)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/assess"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/assess.svg" alt="Measured on agentmods" height="20"></a>What 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.00072 | $0.05985 |
| Opus 5 | $0.00036 | $0.02993 |
| Sonnet 5 | $0.00014 | $0.01197 |
| Haiku 4.5 | $0.00007 | $0.00598 |
Grade A, and why
assess 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 3d 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 — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/assess/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Assess
Comprehensive assessment skill for answering "is this good?" with structured evaluation, scoring, and actionable recommendations.
🎯 Quick Start
/ork:assess backend/app/services/auth.py
/ork:assess our caching strategy
/ork:assess --model=opus the current database schema
/ork:assess frontend/src/components/Dashboard
Effort levels (CC 2.1.111+ adds xhigh)
| Effort | Behavior |
|---|---|
low / medium |
Subset of dimensions, faster turnaround |
high (default) |
All six dimensions with pros/cons |
xhigh |
All six dimensions + one additional assessor pass focused on uncertainty/caveats; emits confidence per dimension |
xhighsilently falls back tohighon a model that does not implement it: no error, no log line./ork:doctorCategory 14 reports this, and only when it can positively prove the active model lacks the tier.
Argument Resolution
Step 0: resolve a conversational reference first
$ARGUMENTS is often not a path. For a bare pronoun or deictic (them, this, that,
these, they, same, the above, the last one, what we just did) or an empty target
after flags are stripped, the subject is in the conversation. Read back for the NEAREST
concrete one (a file just discussed, a diff or PR just opened, a component just investigated)
and announce the resolution in one line, so a wrong guess costs a correction rather than a
turn: "Reading 'them' as the 3 pretool guards we just probed; say otherwise and I'll switch."
Refusing is the bug, not the safe option. Asking "what does this refer to?" when the
previous turn named the subject burns a round-trip re-deriving what is already on screen.
Measured 2026-08-28: the operator sent /ork:assess them throguhly one message after "bug in
orchestkit hooks", mid-investigation of pretool/bash/dangerous-command-blocker, and this
skill replied that "them" had "no antecedent anywhere in this conversation". It had two.
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.
- 3d ago First seen · 453 lines · 72 tokens per session scan A 6fadd5b3f9cb
assess is a command published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 5,985 once invoked, about $0.0004 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
setup
Full onboarding for a new project — runs /doctor diagnostics, then injects the CLAUDE.md template + nav-ref instrumentation + Zustand store exposure so the plugin works without the user having to read documentation.
run-action
Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as /rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with structured RunRecords (GH.
nav-graph
Extract, inspect, and query the app navigation graph — a complete map of all screens and navigators.
vibecoding
Calculate vibecoding index for code quality.
check-env
Check that the fenced React Native session, Metro, app target, and device inventory are ready for testing.
gate
Check SDLC gate status and requirements.