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/ccdawn/vibelution/issue-trackergit clone --depth 1 https://github.com/CCDawn/VibelutionWhat 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.00066 |
| Opus 5 | $0.00000 | $0.00033 |
| Sonnet 5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00007 |
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
This repository uses GitHub Issues as its source of truth for issues, PRDs, and issue-linked agent work.
Repository: CCDawn/Vibelution
Agents should read and update issues through GitHub when an issue workflow is requested. Issue references should use GitHub issue numbers and URLs from this repository.
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 · 8 lines · 0 tokens per session scan A 5365fe828f87
issue-tracker is an agent published in the GitHub repository CCDawn/Vibelution (21 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 66 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
medical-learning-safety-reviewer
审校医学学习草稿的来源、教育边界、患者隐私和输出风险；只返回审校意见，不处理外部动作或状态写入。.
guideline-learning-designer
将主助手已核验的指南材料组织成安全、可继续展开的学习地图、流程关系、学习诊断或复习路径；不处理真实患者决策。.
ingest-confluence
Ingest one Confluence page into an AKB vault as a five-section LLM-wiki summary document, fetched live via the Atlassian MCP server.
ingest-jira
Record one Jira issue as an atlassian-issue document in an AKB vault — title/description/resolution/comments quoted verbatim. Fetched live via the Atlassian MCP server; always upsert.
ingest-doc
Ingest one document (local file or web URL) into an AKB vault as a five-section LLM-wiki summary page, optionally preserving the original bytes in the raw file layer.
ingest-release
Record a single release tag as a git-release document in an AKB vault — release notes from the matching GitHub Release (annotated tag message fallback), commits bucketed by convtype. Requires range commits pre-ingested.