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/clay-good/openlore/issue-trackergit clone --depth 1 https://github.com/clay-good/OpenLoreWhat 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.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
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.
What it actually says
Issue tracker: GitHub
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
gh infers the repository from the clone's remotes. If a clone has several remotes (a
fork setup, say) and the inferred repo is not the one you mean, pass --repo <owner>/<repo>
explicitly rather than letting it guess.
Conventions
- Create an issue:
gh issue create --title "..." --body "...". Use a heredoc for multi-line bodies. - Read an issue:
gh issue view <number> --comments - List issues:
gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'with appropriate--labeland--statefilters. - Comment on an issue:
gh issue comment <number> --body "..." - Apply / remove labels:
gh issue edit <number> --add-label "..."/--remove-label "..." - Close:
gh issue close <number> --comment "..."
Label strings come from triage-labels.md — do not invent new ones.
Write access
A gh write (create, comment, label, close) can fail with HTTP 403 when the account
lacks permission on the target repository. That is a permissions boundary, not a
malformed command: report it and stop. Do not silently retarget the write to another
repository — an issue filed somewhere other than where the skill was told to file it is
worse than none.
When a skill says "publish to the issue tracker"
Create a GitHub issue.
When a skill says "fetch the relevant ticket"
Run gh issue view <number> --comments.
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 · 35 lines · 0 tokens per session scan A cd7255832f03
issue-tracker is an agent published in the GitHub repository clay-good/OpenLore (290 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 422 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
sweep-scan
You are a backlog sweeper. ./input.json names one repo and the exact source tree to read it against.
CLAUDE
Provides specialized subagents for complex operations in team-management, including multi-provider issue tracking synchronization (GitLab, Jira, GitHub / Gitea), code review, and task management automation.
project-planner
Use this agent when the user needs help with project planning, task decomposition, milestone definition, sprint planning, prioritization, effort estimation, roadmap creation, progress tracking, or any project structure-related questions. This agent should be used PROACTIVELY whenever the conversation touches on…
durability-arbiter.eval
Boundary scenarios drawn from real usage-retro evidence, each run through the durability-arbiter agent (sonnet). Re-run by spawning the agent with the agent file as prompt + each consultation. First run 2026-06-22: 8/8 correct.
tech-architect
Propose l architecture technique basee sur les specs et les preferences de reference : stack, modele de donnees, API, infrastructure, securite.
durability-arbiter
Consulted by a running executor at an ambiguous would-stop boundary to decide CONTINUE / ASK / STOP, so the run keeps going autonomously instead of interrupting the user. Plays the user's standing posture with criterion. Read-only and fast.