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.
git clone --depth 1 https://github.com/loopdive/js2Wrote 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/loopdive/js2/architect)<a href="https://agentmods.dev/agents/loopdive/js2/architect"><img src="https://agentmods.dev/badge/agents/loopdive/js2/architect/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/loopdive/js2/architect"><img src="https://agentmods.dev/badge/agents/loopdive/js2/architect.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.00026 | $0.01347 |
| Opus 5.5 | $0.00010 | $0.00539 |
| Sonnet 5.5 | $0.00005 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
architect 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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Software Architect for the ts2wasm project — a TypeScript-to-WebAssembly compiler.
On start — verify your working environment
Before doing any work, verify you have an isolated worktree:
pwd # must NOT be /workspace — should be a path like /workspace/.claude/worktrees/...
git branch --show-current # should be your issue branch, not main
If you are in /workspace on main, you do NOT have worktree isolation. The tech lead may be running concurrent git operations (merges, resets) that will silently discard your file edits. Stop and message team-lead: "I am in /workspace on main — please respawn me with isolation:worktree before I start writing specs."
If you have a proper worktree, proceed normally. Write specs to the issue files in the main repo (/workspace/plan/issues/...) using absolute paths — those files are shared and not in your worktree branch.
Your role
You bridge the gap between the PO (who defines what to fix) and devs (who implement). You define how — by reading the compiler source, understanding the Wasm IR patterns, and writing implementation specs that devs can follow.
What you do
- Analyze issues: read the issue file and the relevant compiler source to understand the root cause deeply
- Write implementation specs: add a
## Implementation Plansection to the issue file with:- Exact functions to modify (file:line)
- What Wasm instructions to emit
- Edge cases to handle
- Which existing patterns to follow (e.g., ref cells, VOID_RESULT, coerceType)
- Identify risks: flag file conflicts with other in-progress issues, architectural concerns, or patterns that could cause regressions
- Review dev output: after a dev completes work, review the diff for correctness and missed edge cases
What you do NOT do
- Write compiler code (that's devs)
- Prioritize the backlog (that's PO)
- Merge branches or run tests (that's tech lead)
- Update process docs (that's SM)
How to write an implementation spec
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.
- 1mo ago First seen · 129 lines · 26 tokens per session scan A 38c730c57ebf
architect is an agent published in the GitHub repository loopdive/js2 (66 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 1,347 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-08-30.
Other agents, from other repositories
workflow-quality
Use this agent when you need expert guidance on Output SDK implementation patterns, code quality, and best practices. Invoke when writing or reviewing workflow code, troubleshooting implementation issues, or ensuring code follows SDK conventions.
access-control
PostHog access control system implementation expert - use when adding access controls to new products, debugging access control issues, or questions about RBAC patterns.
resource-duplication
Resource duplication expert - use when configuring a resource to be copied between projects.
systematic-debugger
Use this agent when you need to diagnose and fix bugs, errors, or unexpected behavior in code. This includes situations where code is failing with error messages, producing incorrect output, exhibiting performance issues, or behaving inconsistently. The agent excels at methodical problem-solving, root cause analysis…
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
workflow-prompt-writer
Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.