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 agents/thixpin/pitway/opencodegit clone --depth 1 https://github.com/thixpin/pitwayWhat 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.00029 | $0.01032 |
| Opus 5 | $0.00015 | $0.00516 |
| Sonnet 5 | $0.00006 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
opencode 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skip to content
OpenCode
OpenCode is an opt-in driver integration: pitway init --opencode.
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.
- yesterday First seen · 91 lines · 29 tokens per session scan A 379d49eae8c0
opencode is an agent published in the GitHub repository thixpin/pitway (19 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 1,032 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 agents, from other repositories
artifact-writer
PACEflow artifact 操作专员。处理索引文件（task / walkthrough / findings / corrections.md）和 changes/ 子目录详情文件的 CRUD。 详细规范在 ${CLAUDEPLUGINROOT}/agent-references/artifact-writer-spec.md 与 ${CLAUDEPLUGINROOT}/agent-references/instructions/。.
adversarial-reviewer
Adversarial reviewer for specs, plans, implementations, or any combination ("spec amendment + implementation in the same PR" is the dominant case). Loads project conventions and the targeted artifacts; attacks along the relevant checklists; returns severity-labeled findings. Use after gates pass but before declaring…
quality-engineer
Quality-lens reviewer covering testability, observability, reliability, and maintainability -- the "cost to live with this code" pass. Also drafts contract or construction tests on request. Reads effective repository guidance, the spec and plan if any, the diff, and nearby tests; flags test-shape problems (wrong…
security-reviewer
Threat-model and secure-design reviewer for changes that cross a security boundary — auth, data handling, dependencies, deserialization, file/network I/O, secrets, or LLM/agent code. Runs in two modes — a spec-stage secure-design pass (is the control specified as an acceptance criterion at the right depth?) and an…
finding-adjudicator
Independent finding adjudication as a distinct work type. Tests each supplied reviewer finding against current repository evidence and authority, returning only sustained findings to the review loop while preserving refuted and indeterminate decisions for audit. Does not discover defects or edit the target.
implementer
Single-task implementer for the work-loop's supervisor mode. Given a plan task, a worktree path, and references to the spec and plan, implements only that task inside the worktree, runs the project's gates (lint, typecheck, tests), and returns a markdown status report (ready / blocked / failed) with a short summary.…