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 skills add AmariahAK/atlarix-skills --skill denogit clone --depth 1 https://github.com/AmariahAK/atlarix-skillsWrote 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/skills/amariahak/atlarix-skills/deno)<a href="https://agentmods.dev/skills/amariahak/atlarix-skills/deno"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/deno/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/skills/amariahak/atlarix-skills/deno"><img src="https://agentmods.dev/badge/skills/amariahak/atlarix-skills/deno.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.00003 | $0.00348 |
| Opus 5 | $0.00002 | $0.00174 |
| Sonnet 5 | $0.00001 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
Deno Patterns 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 8d 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
Deno Patterns
When to use this skill
Use this skill when working on Deno projects and you want predictable module imports, permission-aware runtime behavior, and clean project structure.
Core patterns
Permissions are part of the contract
Deno requires explicit permissions. Make them intentional:
--allow-netfor network--allow-readfor filesystem reads- avoid
--allow-allin production scripts
Project structure
Common:
deno.json/deno.jsoncmod.tsas entrypoint for librariesmain.tsfor apps
Dependency management
- prefer import maps
- keep third-party imports centralized
Testing
- use
deno test - keep tests deterministic
Atlarix tool notes
- Explore: inspect
deno.jsonand entrypoints; trace imports. - Build: run
deno testanddeno fmtif configured. - Debug: check permission errors first; they’re common.
- Review: verify permission flags are minimal and documented.
Common mistakes to avoid
- Using
--allow-allby default - Scattering dependencies across files
- Ignoring permission failures and “fixing” by widening permissions
Mini-checklist
- Minimal permissions
- Imports centralized
- Tests use deno tooling
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.
- 8d ago First seen · 53 lines · 3 tokens per session scan A 15daad7d3682
Deno Patterns is a skill published in the GitHub repository AmariahAK/atlarix-skills (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3 tokens to every session and 348 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
typescript-project
Modern TypeScript project architecture guide for 2025. Use when creating new TS projects, setting up configurations, or designing project structure. Covers tech stack selection, layered architecture, and best practices.
typescript-best-practices
TypeScript/Node.js best practices. Use when writing or reviewing TypeScript code. Covers type safety, async patterns, and error handling.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
bun-runtime
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
typescript
TypeScript strict mode with eslint and jest.
codebase-architecture
Designs module contracts, deepens existing boundaries, and installs enforceable repository guardrails. Use when asked to "design the architecture", "simplify our modules", or "harden the repo". For one feature plan use planning; for diff cleanup use tidy; for tenancy use multi-tenant-architecture.