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/moabualruz/fulcrum/issue-trackergit clone --depth 1 https://github.com/moabualruz/fulcrumWrote 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/agents/moabualruz/fulcrum/issue-tracker)<a href="https://agentmods.dev/agents/moabualruz/fulcrum/issue-tracker"><img src="https://agentmods.dev/badge/agents/moabualruz/fulcrum/issue-tracker.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00257 |
| Opus 5 | $0.00000 | $0.00129 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
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 4d 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.
What it actually says
Issue tracker: local markdown
Issues and PRDs for this repo live as markdown files in a session-chosen working directory on the user's local machine. They are NOT tracked in git. The orchestrator (or the user) names a working root and tells the agent; the conventions below describe the file shape independent of where the root happens to be.
Conventions
- One feature per directory:
<root>/<feature-slug>/ - The PRD is
<root>/<feature-slug>/PRD.md - Implementation issues are
<root>/<feature-slug>/issues/<NN>-<slug>.md, numbered from01 - Triage state is recorded as a
Status:line near the top of each issue file (seetriage-labels.mdfor the role strings) - Comments and conversation history append to the bottom of the file under a
## Commentsheading
When a skill says "publish to the issue tracker"
Create a new file under <root>/<feature-slug>/ (creating the directory if needed), using whatever working root the current session is using.
When a skill says "fetch the relevant ticket"
Read the file at the referenced path. The user will normally pass the path or the issue number directly.
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.
- 4d ago First seen · 20 lines · 0 tokens per session scan A 17a45165ca5c
issue-tracker is an agent published in the GitHub repository moabualruz/fulcrum (3 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 257 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
board-haiku
Mechanical delivery-board executor (haiku tier). Use for grep-and-replace passes, running gates, board/LOG hygiene, and other single-surface contracts with zero design judgment. Also see board-verifier for verification work.
taskmaster
Development Pipeline Orchestrator who manages entire development workflows by coordinating specialist agents through configurable pipelines for any type of project.
codecrusher
Senior Developer & Implementation Expert who transforms architectural plans into high-quality, production-ready code across any technology stack.
ship-and-babysit
Commit local changes, push the branch to the user's fork, open or reuse a PR against tinyhumansai/openhuman:main, then babysit CI and CodeRabbit feedback until the PR is green and clean. Use when the user wants an end-to-end ship flow, not just implementation.
mobile-agent
Specializes in Android and iOS development, handling platform-specific configurations and debugging.
dev-agent
Assists with day-to-day development tasks, code generation, and feature implementation.