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/acryldev/acryl/issue-trackergit clone --depth 1 https://github.com/acryldev/acrylWhat 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.00000 | $0.00700 |
| Opus 5 | $0.00000 | $0.00350 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
issue-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: specs/ (local Spec Kit + Wayfinder)
Issues, specs (PRDs), and Wayfinder maps for this repo live as markdown under
specs/. GitHub remote is acryldev/acryl; GitHub Issues are an
optional promotion surface, not the default store.
This is intentional: ACRYL is built by many coding agents, some without gh
auth, and the user asked for a specs/ tree as the feature-block store.
Conventions
- One implementation milestone per directory:
specs/<NNN-slug>/ - Spec Kit artifacts in that directory:
spec.md— feature specification (/speckit-specify, also a Matt Pocock PRD)plan.md— technical plan (/speckit-plan)tasks.md— ordered implementation tasks (/speckit-tasks)research.md— facts the plan waits on
- Do not collapse implementation tickets into one mega file once a
milestone is being built. If
/to-ticketsruns, writespecs/<NNN-slug>/issues/<NN>-<slug>.md, numbered from01. - Triage state is a
Status:line near the top of each issue file (seetriage-labels.md). - Comments append under a
## Commentsheading.
When a skill says "publish to the issue tracker"
Create or update a file under specs/<feature-slug>/ (creating the directory
if needed). Prefer spec.md for a full PRD.
When a skill says "fetch the relevant ticket"
Read the referenced path. The user will normally pass the path or the
NNN-slug / issue number.
Wayfinding operations
Used by /wayfinder. The map is a file with one child file per ticket.
- Map:
specs/000-wayfinding/map.md— Destination / Notes / Decisions-so-far / Not yet specified / Out of scope. - Child ticket:
specs/000-wayfinding/issues/NN-<slug>.md, numbered from01. Body holds## Question. Header lines:Type: research | prototype | grilling | taskStatus: open | claimed | resolvedBlocked by: [ticket title](relative/path.md)(optional; never a bare ID)
- Blocking: a ticket is unblocked when every file listed in
Blocked byisStatus: resolved. - Frontier: scan
specs/000-wayfinding/issues/for files that are notresolved, have no unresolved blockers, and are notclaimed. Lowest number wins. - Claim: set
Status: claimedand save before any work. - Resolve: append the answer under
## Answer, setStatus: resolved, then append a one-line gist + relative link to the map's Decisions-so-far.
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 · 59 lines · 0 tokens per session scan A fae967db1e92
issue-tracker is an agent published in the GitHub repository acryldev/acryl (220 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 700 tokens. 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
design-reviewer
Design document reviewer — verifies every claim against codebase facts, checks mechanism feasibility, finds root causes of errors, and delivers structured findings by severity.
spec
计划型 primary agent（spec 模式，v0.4.0 = 无路由干预 deep-think）。system 保持 opencode 原生组装（含 AGENTS.md/环境告知），路由插件对 spec 会话零干预；工具面读优先：read/glob/grep/websearch 放行，edit/write 需确认。适用于架构设计、方案评审、复杂任务规划——读随便、写要问。.
GIT-COLLAB
主 Agent（lead）负责拆分 Issue；其它 Agent 认领 → 拉分支 → 实现 → 提 MR → 由 lead 合回 main。 本机版本控制命令统一用 hutao。.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.