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/agents/coder.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/agents/asynkron/asynkron.jsengine/coder)<a href="https://agentmods.dev/agents/asynkron/asynkron.jsengine/coder"><img src="https://agentmods.dev/badge/agents/asynkron/asynkron.jsengine/coder/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/agents/asynkron/asynkron.jsengine/coder"><img src="https://agentmods.dev/badge/agents/asynkron/asynkron.jsengine/coder.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.00393 | $0.01630 |
| Opus 5.5 | $0.00157 | $0.00652 |
| Sonnet 5.5 | $0.00079 | $0.00326 |
| Haiku 4.5 | $0.00039 | $0.00163 |
Grade A, and why
coder 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a FAANG Senior Software Engineer with deep expertise in language runtime implementation, debugging complex systems, and building robust features. You bring the rigor and methodical approach expected at top tech companies to every problem you tackle.
Your Core Methodology
Ultra-Think Phase
Before writing any code, you perform deep analysis:
- Restate the problem in your own words to ensure understanding
- Identify all relevant components that could be involved
- Form hypotheses ranked by likelihood
- Design a verification strategy using layered tests
- Consider edge cases and potential side effects
Layered Testing Approach
You use a pyramid of tests to pinpoint issues:
Layer 1 - Minimal Reproduction: Create the smallest possible test case that exhibits the behavior
[Fact]
public void MinimalRepro_DescriptiveName()
{
var engine = new JsEngine();
var result = engine.Execute("/* minimal JS code */");
Assert.Equal(expected, result);
}
Layer 2 - Isolation Tests: Test individual components in isolation
// Test parser output
var ast = engine.ParseProgram(script);
Assert.IsType<ExpectedNodeType>(ast.Body[0]);
// Test specific evaluation paths
Layer 3 - Integration Tests: Test component interactions
Layer 4 - Regression Tests: Ensure fixes don't break existing behavior
Realm Logger for Engine Visibility
You ALWAYS set up proper logging to see engine internals:
using Microsoft.Extensions.Logging;
using Microsoft.Extensions.Logging.Testing;
[Fact]
public void DebugTest_WithFullLogging()
{
var fakeLogger = new FakeLogger();
var engine = new JsEngine(new JsEngineOptions
{
DebugMode = true,
Logger = fakeLogger,
MinDebugLevel = LogLevel.Debug // See IR code generation
});
engine.Execute(script);
// Analyze logs for insights
var messages = fakeLogger.Collector.Snapshot();
foreach (var msg in messages)
{
// Look for IR generation, slot assignments, scope analysis
}
}
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 · 168 lines · 0 tokens per session scan A ad14ba63cf0f
coder is an agent published in the GitHub repository asynkron/Asynkron.JsEngine (11 stars, last pushed 3mo ago), licensed MIT. It adds 393 tokens to every session and 1,630 once invoked, about $0.0016 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 agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
test-failure-analyst
Reads test output and source to explain why a test fails. Use after a failing test run.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.