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.
git 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/iterate-research)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/iterate-research"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/iterate-research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/yonatangross/orchestkit/iterate-research"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/iterate-research.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00054 | $0.00456 |
| Opus 5.5 | $0.00022 | $0.00182 |
| Sonnet 5.5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
iterate-research 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 today.
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
Auto-generated from skills/iterate-research/SKILL.md
Source: https://github.com/yonatangross/orchestkit
iterate-research
Revise one research file. The body is rewritten from fresh reading of the code; the comment block is
kept byte for byte. Layout: the create-plan skill's references/artifact-layout.md.
Steps
-
Read the research in full and list its open comments:
node "skills/iterate-research/scripts/artifact.mjs" list --file <research> --open -
Re-check every challenged claim in the code, at the current commit. If the code moved since the artifact's
sha, say which findings changed. -
New questions get the same method as create-research: parallel
Exploreagents by area, citations checked by you. -
Write the revised body to a scratch file (no comment block in it) and write it back:
node "skills/iterate-research/scripts/artifact.mjs" iterate --file <research> --body /tmp/research-body.md -
Reply to each comment you addressed (
reply, orresolvewhen the reviewer asked or the comment was a factual correction you made), then answer with the path, the revision and the comments still open.
Rules
- Same rules as create-research: describe, cite, no recommendations.
- Never edit the file with Write or Edit, and never delete a comment.
Related
/ork:create-researchwrites the first revision./ork:review-artifact-commentshandles comments without a rewrite.
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.
- today First seen · 49 lines · 54 tokens per session scan A 5725ee085334
iterate-research is a command published in the GitHub repository yonatangross/orchestkit (298 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 456 once invoked, about $0.0002 per session on Opus 5.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-10-27.
Other commands, from other repositories
gc
On-demand code-drift / entropy scan (garbage collection) via a fresh-context drift-analyst subagent. Checks changed/active code against golden-rules.md + generic drift heuristics (dead code, duplication, doc-drift) and reports findings with an evidence path. Read-only — recommends, never auto-refactors. Not git gc.
pn-audit-api
Surgical API design review — REST conventions, status codes, response shapes, validation, and schema leaks. Use standalone or as part of pn-backend-audit. Outputs a scored fix roadmap.
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.
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.