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/stonematt/mcp-obsidian-cli/issue-trackergit clone --depth 1 https://github.com/stonematt/mcp-obsidian-cliWhat 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.00851 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker: GitHub
Issues for this repo live as GitHub Issues, grouped by GitHub Milestones, modeled on the nitimini workflow. Use the gh CLI for all operations.
Three-level hierarchy
| Level | Artifact | Lives in | Lifecycle |
|---|---|---|---|
| Roadmap | direction, themes | README.md (or docs/product/ROADMAP.md if it grows) |
durable |
| Brief / PRD | scoped initiative | docs/briefs/<name>.md + GitHub Milestone |
per-initiative |
| Issue | vertical slice | GitHub Issue | flows the status state machine |
The brief carries the why and architecture. Each child issue carries the what and acceptance criteria — issue bodies must stand alone so an agent can pick one up without reading back to the brief.
PRDs are not issues. When /to-prd produces a PRD, it writes the document to docs/briefs/<name>.md, creates a Milestone pointing at it, and stops. /to-issues then slices the brief into child issues under that Milestone.
Conventions
- Create an issue:
gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies. New issues open atstatus: triage. - Read an issue:
gh issue view <number> --comments. - List issues:
gh issue list --state open --json number,title,body,labels,milestone,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], milestone: .milestone.title, comments: [.comments[].body]}]'with appropriate--label,--milestone,--statefilters. - Comment:
gh issue comment <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Assign to milestone:
gh issue edit <number> --milestone "<title>" - Close:
gh issue close <number> --reason "completed|not planned" -c "..." - Create milestone:
gh api repos/:owner/:repo/milestones -f title="..." -f description="See docs/briefs/<name>.md"
gh auto-detects the repo from git remote -v when run inside a clone.
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 · 45 lines · 0 tokens per session scan A 6c6dee05fae6
issue-tracker is an agent published in the GitHub repository stonematt/mcp-obsidian-cli (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 851 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
gtd-project-manager
Autonomous project coordination agent that tracks project status, identifies blockers and dependencies, calculates completion percentages, flags timeline risks, and suggests follow-up tasks. Proactively escalates blockers older than 7 days. Invoked by ai-task-executor for :AI:pm: tagged tasks.
pkm-capture
Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…
link-auditor
Use proactively in the background after creating or modifying multiple vault notes, or when asked about vault link health. Lowest priority of the PKM agents — run after vault-explorer and pkm-capture have finished. Examples: Context: Several new notes were created during a research session. user: "OK I think we've…
vault-explorer
Use proactively when researching what the vault knows about a topic, before creating new notes, or when exploring existing knowledge and connections. Run in foreground — results inform the caller's next steps. Examples: Context: User asks about a topic before creating new content. user: "What does the vault already…
backlog-groomer
For one operator's assigned beads, finds what is ready/urgent to sprint next, proposes cohesive sprint sets from interdependencies, finds duplicates, and surfaces high-priority/urgent-sounding items whose content quality is too low to act on. Full beads mutation authority (merge/close/defer/reject), always…
plan-reviewer
Reviews beads DAG structure for coverage, task size, and acceptance criteria; classifies each task complexity bucket and reads its assigned model; returns APPROVED or CHANGESNEEDED.