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/KeenBrain/awesome-ai-resourcesWrote 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/keenbrain/awesome-ai-resources/manage-linear-tickets)<a href="https://agentmods.dev/commands/keenbrain/awesome-ai-resources/manage-linear-tickets"><img src="https://agentmods.dev/badge/commands/keenbrain/awesome-ai-resources/manage-linear-tickets/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/keenbrain/awesome-ai-resources/manage-linear-tickets"><img src="https://agentmods.dev/badge/commands/keenbrain/awesome-ai-resources/manage-linear-tickets.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.00026 | $0.00664 |
| Opus 5 | $0.00013 | $0.00332 |
| Sonnet 5 | $0.00005 | $0.00133 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
manage-linear-tickets 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 12d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 12d ago First seen · 82 lines · 26 tokens per session scan A 64b71798695e
manage-linear-tickets is a command published in the GitHub repository KeenBrain/awesome-ai-resources (5 stars, last pushed 7mo ago), with no licence file. It adds 26 tokens to every session and 664 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-31.
Other commands, from other repositories
todos-to-issues
I'll scan your codebase for TODO comments and create professional GitHub issues following your project's standards.
init-project
Initialize project with CLAUDE.md template - adaptive detection for new or existing projects.
handoff
You are generating a self-contained briefing optimized for a successor — someone who needs to continue this sprint, not a stakeholder making a decision. Read CLAUDE.md, claims.json, and compilation.json.
merge
You are merging claims from another sprint into the current one. This is for when two teams researched the same problem independently and need to combine their findings.
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…