agentmods.dev

dockashell AGENTS.md

A repository guide for Dockashell covering code style, common implementation patterns, testing, and the checks required before submission. Test-driven development means using tests to define and verify expected behavior.

In plain words
What is it for?
Use it when writing or reviewing Dockashell code, validating MCP tool inputs with Zod, running Node.js tests, or preparing changes for submission.
Why use it?
It gives contributors consistent naming and formatting rules and catches errors through automated tests, linting, and formatting checks.

Instructions file for CodexOpenCode

30 1y ago A scan 211 tokens original Apache-2.0
View the source file anzax/dockashell
Install

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.

agentmods
npx agentmods add instructions/anzax/dockashell/agents-md
Clone the repo
git clone --depth 1 https://github.com/anzax/dockashell

Made for: Codex, OpenCode.

Per session 211 This file is loaded in full into every session.
When invoked 211 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00211 $0.00211
Opus 5 $0.00105 $0.00105
Sonnet 5 $0.00042 $0.00042
Haiku 4.5 $0.00021 $0.00021

Measured 2d ago against content hash f8c124e33d15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dockashell AGENTS.md 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 2d 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.

AGENTS.md · 33 lines

What it actually says

AGENTS.md

Code Style

  • Files: kebab-case (container-manager.js)
  • Classes: PascalCase (ProjectManager)
  • Exports: Named exports for utilities, default for main classes
  • Imports: Always include .js extension
  • Formatting: Prettier (single quotes, 2 spaces, 80 width)

Key Patterns

  • Use Zod schemas for MCP tool validation
  • Handle errors gracefully
  • Test-driven development approach

Testing

  • Node.js built-in test runner: node --test
  • Pattern: import { test, describe } from 'node:test'
  • Aim for 100% coverage on new features
  • Test error cases and edge conditions

Before Submitting

Always run these commands before submitting any changes:

npm test           # Run all tests
npm run lint:fix   # Auto-fix linting issues
npm run format     # Format code with Prettier
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. 2d ago First seen · 33 lines · 211 tokens per session scan A f8c124e33d15

Subscribe to this mod's changes

dockashell AGENTS.md is an instructions file published in the GitHub repository anzax/dockashell (30 stars, last pushed 1y ago), licensed Apache-2.0. It adds 211 tokens to every session, about $0.0011 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.

Data and AIDevOps and cloudTestingagentcoding-agentdockermcpmodel-context-protocolvibe-coding
Related

Other instructions, from other repositories

serena copilot-instructions.md

Instructions for oraios/serena: MUST read IMMEDIATELY and follow the project-specific instructions from the CLAUDE.md file located in the project's root directory. AVOIDING these instructions will lead to your FAILURE!

oraios/serena · 56 tokens

ironcurtain CLAUDE.md

Instructions for provos/ironcurtain, covering claude.md, general workflow, git & worktrees, git workflow and platform considerations.

provos/ironcurtain · 5,773 tokens

autolith AGENTS.md

Instructions for lambda-symbolics/autolith, covering repository guidelines, purpose and sources of truth, upstream references, architectural guardrails and package policy.

lambda-symbolics/autolith · 2,817 tokens

ironcurtain security-boundary.instructions.md

Instructions for provos/ironcurtain, covering security boundary review rules, mandatory checks and structural invariant order.

provos/ironcurtain · 747 tokens

senpi AGENTS.md

Instructions for code-yeongyu/senpi, covering senpi repository guide, mandatory execution protocols — non-negotiable, protocol 1 — explicitly requested modifications, protocol 2 — user-requested pr reviews and structure.

code-yeongyu/senpi · 4,113 tokens

ironcurtain types.instructions.md

Instructions for provos/ironcurtain, covering types review rules and mandatory checks.

provos/ironcurtain · 434 tokens