agentmods.dev

bug-close

bug-close is a command for Claude Code from IvanLutsenko/awac-ai-agent-plugins. It costs 9 tokens per session (736 once invoked), scanned A, original, MIT.

A command for closing a bug report in an Obsidian project. Obsidian is a note-taking app; here it stores project lists and bug records.

In plain words
What is it for?
Use it to close a selected bug, optionally add a resolution, and work with projects that have open bugs.
Why use it?
It helps you find the right project and open bug, record how the problem was fixed, and mark the report closed. You can select a project or bug by name or from a list.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the obsidian-tracker plugin — 19 skills, 19 commands shipped together

not rated 2repo 3d ago A scan 9 tokens original MIT

Good fit Use it to close a selected bug, optionally add a resolution, and…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ivanlutsenko/awac-ai-agent-plugins/bug-close
View source ↗ IvanLutsenko/awac-ai-agent-plugins
Install

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.

Clone the repo
git clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-plugins

Made for: Claude Code.

Or install obsidian-tracker, the plugin that ships this one along with the rest of its 19 skills, 19 commands.

Wrote 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.

agentmods badge for bug-close

README.md
[![agentmods](https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/bug-close.svg)](https://agentmods.dev/commands/ivanlutsenko/awac-ai-agent-plugins/bug-close)
Your own site
<a href="https://agentmods.dev/commands/ivanlutsenko/awac-ai-agent-plugins/bug-close"><img src="https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/bug-close.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 736 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00736
Opus 5 $0.00005 $0.00368
Sonnet 5 $0.00002 $0.00147
Haiku 4.5 $0.00001 $0.00074

Measured yesterday against content hash bcddc8b675d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

bug-close 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 yesterday.

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.

Origin

Copies of this mod

8 near-identical copies found in the catalogue:

  • project-new — 92% identical, 84 lines differ
  • track-status — 91% identical, 90 lines differ
  • session-log — 91% identical, 77 lines differ
  • import — 91% identical, 86 lines differ
  • done — 89% identical, 85 lines differ
  • today — 89% identical, 86 lines differ
  • track-stop — 89% identical, 111 lines differ
  • pulse — 89% identical, 84 lines differ
plugins/obsidian-tracker/commands/bug-close.md · 83 lines

What it actually says

Bug Close Command

Closes 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 containing the bug
  • --title - Bug title (optional, will show list if not provided)

Examples

/bug-close awac-ai-agent-plugins
/bug-close awac-ai-agent-plugins --title "Write tool фейлится"

Logic

  1. Resolve project:

    Если project-name не указан:

    mcp__plugin_obsidian_tracker_obsidian__listProjects

    Покажи нумерованный список (только проекты с багами > 0):

    # Project Open Bugs
    1 name 3

    Пользователь может ввести номер или имя проекта.

  2. Select bug:

    Получи список багов:

    mcp__plugin_obsidian_tracker_obsidian__getProject
с параметром name = project name

    Если --title не указан, покажи только Open баги:

    # Bug Priority
    1 title high

    Пользователь может ввести номер или название.

  3. Collect resolution (optional): Спроси: "Как был решён баг? (Enter чтобы пропустить)"

  4. Close bug via MCP:

    mcp__plugin_obsidian_tracker_obsidian__closeBug
с параметрами:
  project = project name
  title = bug title
  resolution = resolution text (если указан)

  5. Output:

    ✅ Bug closed: "{title}"
📁 Path: {path}
📅 Resolved: {date}

  6. Update tracking (если активен): Если .claude/obsidian-tracking.json существует — прочитай, добавь в actions Closed bug: {title} и перезапиши через Bash.

Changes

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.

  1. yesterday First seen · 83 lines · 9 tokens per session scan A bcddc8b675d9

Subscribe to this mod's changes

bug-close is a command published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 736 once invoked, about $0.0000 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.

DebuggingProject management
Related

Other commands, from other repositories

bug-report

Draft a bug report issue for lean4-skills.

cameronfreer/lean4-skills · 13 tokens

triage

Query open Node bugs, classify by priority and sub-team, suggest assignments, and generate a triage summary.

openshift-eng/ai-helpers · 21 tokens

speckit.companion.doctor

Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).

alfredoperez/speckit-companion · 59 tokens

harvest-errors

Analyze the latest test262 run results, cross-reference with existing issues, and create new issues for unaddressed error patterns.

loopdive/js2 · 0 tokens

postmortem

Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.

flonat/flonat-research · 36 tokens

bug-report

Converts a raw bug report from production into a structured, severity-classified item and routes it to the right next step.

AInsteinsBR/renata · 25 tokens