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/npatten/clew/issue-trackergit clone --depth 1 https://github.com/npatten/ClewWhat 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.00366 |
| Opus 5 | $0.00000 | $0.00183 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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 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.
What it actually says
Issue tracker: Clew
Work items for this repo live in Clew, not GitHub Issues.
GitHub is the code remote only. Do not suggest or use GitHub Issues for project work unless the user explicitly asks for GitHub integration.
Canonical commands
Always invoke Clew from the repository root as clew.
- List work:
clew list - Read a work item:
clew show <id> - Create a work item:
clew new "Title" - Start work:
clew start <id> - Finish work:
clew done <id>
Prefer creating increments with a markdown body supplied on stdin:
clew new "Title here" <<'EOF'
## Goal
...
EOF
When a skill says "issue"
Interpret "issue" as a Clew increment.
Use Clew vocabulary in user-facing output where possible:
- Say Increment instead of issue/ticket.
- Say Task for checkboxes inside an increment.
- Say Tag for lightweight labels.
- Say Status only for Clew lifecycle state.
When a skill says "publish to the issue tracker"
Create one or more Clew increments with clew new.
Publish dependency order first: blockers before blocked increments, so later increment bodies can reference earlier IDs.
When a skill says "fetch the relevant ticket"
Use clew show <id> and read the full increment text before acting.
Direct markdown edits
Direct edits to .clew/ files are acceptable for backlog sharpening, metadata tweaks, tags, and body edits when clearer than CLI ceremony.
Prefer CLI commands for lifecycle transitions with side effects, especially start, done, and abandon when available/documented.
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 · 52 lines · 0 tokens per session scan A a68dc43909b4
issue-tracker is an agent published in the GitHub repository npatten/Clew (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 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-31.
Other agents, from other repositories
mcp-connection
Connect Claude Code or any MCP-compatible agent to your Projektor instance.
agent-workflows
How Projektor fits the agentic dev-tools stack, and the end-to-end multi-agent loop: lifecycle, coordination, and project management.
tool-catalog
Every MCP tool Projektor exposes, generated from source.
rest-endpoints
The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.
workflow-spec
The canonical agent workflow rules: definition of ready, state machine, human gates, WIP limits.
flow-metrics
Every metric getflowmetrics returns, what it measures, and how to read it.