Asynkron.JsEngine: Command for Claude Code

.claude/commands/bugreport.md

bugreport is a command for Claude Code from asynkron/Asynkron.JsEngine. It costs 13 tokens per session (749 once invoked), scanned A, original, MIT.

A procedure for turning verified failing tests into GitHub issues, which are tracked work items in a code repository. It checks the failure first, looks for duplicate reports, and records the error and relevant code context.

In plain words
What is it for?
Use it when reporting failing .NET or Test262 tests, including their messages, stack traces, assertions, test code, related source files, and specification references.
Why use it?
It prevents filing issues for failures that cannot be reproduced and reduces duplicate reports. The collected output gives maintainers enough detail to investigate the problem.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is asynkron/Asynkron.JsEngine's own configuration. It tells Claude Code how to work on Asynkron.JsEngine itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Asynkron.JsEngine configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/asynkron/Asynkron.JsEngine/main/.claude/commands/bugreport.md
Clone the repo
git clone --depth 1 https://github.com/asynkron/Asynkron.JsEngine

Made for: Claude Code.

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 bugreport

README.md
[![agentmods](https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/bugreport/github.svg)](https://agentmods.dev/commands/asynkron/asynkron.jsengine/bugreport)
Your own site
<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.

agentmods 80×15 button for bugreport

Your own site · 80×15
<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>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 749 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.00013 $0.00749
Opus 5.5 $0.00005 $0.00300
Sonnet 5.5 $0.00003 $0.00150
Haiku 4.5 $0.00001 $0.00075

Measured 14d ago against content hash 7469f36e7bee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/commands/bugreport.md · 130 lines

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 )"

Read the full file on GitHub · 130 lines

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. 14d ago First seen · 130 lines · 0 tokens per session scan A 7469f36e7bee

Subscribe to this mod's changes

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.