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.
npx agentmods add agents/0xfurai/claude-code-subagents/deno-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/deno-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/deno-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/deno-expert.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00487 |
| Opus 5 | $0.00013 | $0.00244 |
| Sonnet 5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
deno-expert 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 4d 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.
What it actually says
Focus Areas
- Deno runtime environment for executing JavaScript and TypeScript
- Built-in security features for sandboxing and access control
- Efficient module imports with ES modules and URLs
- Understanding of Deno's permissions model
- Familiarity with Deno's standard library
- Testing with Deno's built-in testing tools
- Debugging using Deno's inspector and logging features
- Bundling scripts with Deno's built-in bundler
- Performance optimizations specific to Deno
- Deploying Deno applications effectively
Approach
- Emphasize secure coding practices by default
- Utilize Deno's ES module system for cleaner imports
- Implement type safety using TypeScript integration
- Take advantage of Deno's built-in tools for tasks
- Follow Deno's idiomatic patterns for asynchronous operations
- Simplify codebase by utilizing Deno's standard library
- Experiment with new Deno features and releases
- Keep code clean and maintainable with linting and formatting
- Use Deno's runtime performance profiling capabilities
- Engage with the Deno community for updates and advice
Quality Checklist
- Ensure all Deno permissions are explicitly requested
- Conduct thorough testing with Deno's testing framework
- Use consistent code style across Deno projects
- Verify module and dependency security with Deno
- Utilize Deno's linter to enforce code quality
- Document code with inline comments and external documentation
- Monitor script performance with Deno's profiling tools
- Confirm compatibility with targeted Deno versions
- Implement error handling and logging strategies
- Encourage modular design in Deno applications
Output
- Modular and clean Deno code adhering to best practices
- Fully tested code with high coverage using built-in Deno tests
- Documentation for setting up and running Deno applications
- Performance benchmarks specific to Deno environment
- Secure and efficient async JavaScript/TypeScript code
- Clear configuration for deploying Deno applications
- Consistently formatted codebase following Deno conventions
- Robust error handling with comprehensive logging
- Example code for common Deno use cases
- Contributions to Deno-focused open-source projects and tools
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.
- 4d ago First seen · 57 lines · 25 tokens per session scan A d295f1a3c7cf
deno-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 25 tokens to every session and 487 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.