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 skills add IvanLutsenko/awac-ai-agent-plugins --skill project-buggit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/skills/ivanlutsenko/awac-ai-agent-plugins/project-bug)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/project-bug"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/project-bug.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.1 | $0.00029 | $0.00562 |
| Opus 5 | $0.00015 | $0.00281 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
obsidian-tracker-project-bug 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
Converted from Claude Code command
/project-bug. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.
Project Bug Command
Creates a bug report in the specified project.
Step 0: Check Configuration
Вызови MCP tool:
mcp__plugin_obsidian_tracker_obsidian__getConfig
Если initialized: false: выполни инициализацию как в /projects команде.
Arguments
project-name(optional) - Project to add bug to--title- Bug title (optional, will ask if not provided)--priority- Priority: critical|high|medium|low (default: medium)
Examples
/project-bug awac-ai-agent-plugins
/project-bug awac-ai-agent-plugins --title "Search broken" --priority high
Logic
-
Resolve project:
Если project-name не указан:
mcp__plugin_obsidian_tracker_obsidian__listProjectsПокажи нумерованный список:
# Project Status 1 name Active Пользователь может ввести номер или имя проекта.
-
Collect bug info via AskUserQuestion:
- Title (если не передан через --title)
- Priority: critical / high / medium / low
- Description (multi-line)
-
Create bug via MCP:
mcp__plugin_obsidian_tracker_obsidian__addBug с параметрами: project = project name title = bug title description = description priority = priority -
Output:
🐛 Bug created: "{title}" 📁 Path: {path} 🔴 Priority: {priority} -
Auto-start tracking (если ещё не активен): Если
.claude/obsidian-tracking.jsonне существует — создай через скрипт:plugins/obsidian-tracker/scripts/start-tracking.sh "{project}" "Bug: {title}" "Created bug: {title}"Выведи:
Tracking started for {project}Если файл существует — прочитай его через Read, добавь в actions
Created bug: {title}и перезапиши через Bash.
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 · 81 lines · 29 tokens per session scan A d7f65ba354cd
obsidian-tracker-project-bug is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 562 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-09-05.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
issue-triage
A Chinese-language workflow for handling GitHub issues, from reading the full report through technical diagnosis, classification, decision-making, and drafting a reply. GitHub issues are discussions about bugs, questions, or requested features.