Borrowing it
Nothing to install: this file belongs to asynkron/Asynkron.JsEngine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/asynkron/Asynkron.JsEngine/main/.claude/commands/bugreport.mdgit clone --depth 1 https://github.com/asynkron/Asynkron.JsEngineWrote 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/commands/asynkron/asynkron.jsengine/bugreport)<a href="https://agentmods.dev/commands/asynkron/asynkron.jsengine/bugreport"><img src="https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/bugreport/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/asynkron/asynkron.jsengine/bugreport"><img src="https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/bugreport.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00749 |
| Opus 5.5 | $0.00005 | $0.00300 |
| Sonnet 5.5 | $0.00003 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
bugreport 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 14d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Report for Failing Tests
Create comprehensive GitHub issues for failing tests, avoiding duplicates.
Process
0. Verify Test Failures (if test names provided)
If the user provides test names or a test filter, first run those specific tests to verify the failures:
# For specific test names
dotnet test tests/Asynkron.JsEngine.Tests --filter "FullyQualifiedName~{TestName}" -v detailed 2>&1
# For Test262 tests
dotnet test tests/Asynkron.JsEngine.Tests.Test262 -c Release \
--settings tests/Asynkron.JsEngine.Tests.Test262/LanguageTests.runsettings \
--filter "FullyQualifiedName~{TestName}" -v detailed 2>&1
IMPORTANT: Read and analyze the test output carefully. Extract:
- The exact error message
- The stack trace showing where the failure occurred
- Any assertion details (expected vs actual values)
- The test's JavaScript code if visible
1. Gather Context for Each Failing Test
For each failing test:
a) Search for relevant source files
Use Grep to find related implementation code:
# Search for key types/methods mentioned in the stack trace
b) Check spec.md for relevant specification sections
If the test relates to a specific ECMAScript feature (e.g., generators, async/await, destructuring):
# Search spec.md for relevant sections
Link to line numbers in spec.md that define the expected behavior.
c) Find the test source
# Locate the test file to understand what it's testing
2. Check if issue already exists
gh issue list --search "bug: {TestName} in:title" --state all --json number,title,state --limit 5
If an issue exists (open or closed), report it and skip to the next test.
3. Create new issue with comprehensive details
gh issue create \
--title "bug: {TestName}" \
--assignee "@copilot" \
--body "$(cat <<'EOF'
## Failing Test
**Test:** `{FullyQualifiedTestName}`
**Test File:** [{TestFileName}]({RelativePathToTestFile})
## Test Output
{RelevantTestOutputQuoted}
## Error
{ErrorMessage}
## Stack Trace
{StackTrace}
## Relevant Source Files
{ListOfRelevantSourceFilesWithLinks}
- [`{FileName}`]({RelativePath}): {BriefDescription}
## ECMAScript Specification Reference
{IfApplicable}
- [spec.md L{LineNumber}]({LinkToSpecLine}): {RelevantSpecQuote}
## Context
{WhatTheTestValidatesAndPossibleRootCause}
## Suggested Investigation
{AreasToInvestigate}
## Reproduction
```bash
dotnet test tests/Asynkron.JsEngine.Tests --filter "FullyQualifiedName~{TestName}"
Auto-generated by /bugreport EOF )"
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.
- 14d ago First seen · 130 lines · 0 tokens per session scan A 7469f36e7bee
bugreport is a command published in the GitHub repository asynkron/Asynkron.JsEngine (11 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 749 once invoked, about $0.0001 per session on Opus 5.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-10-02.
Other commands, from other repositories
bug-report
Draft a bug report issue for lean4-skills.
triage
Query open Node bugs, classify by priority and sub-team, suggest assignments, and generate a triage summary.
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).
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.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
harness:maintenance-pipeline
On-demand, report-first maintenance sweep — runs overdue checks via harness maintenance run, triages findings, and asks the human in plain text before dispatching any fix.