AGENTS

Project instructions for work inside the src/commands directory, covering command-line behaviour, validation, error messages, and required checks.

In plain words
What is it for?
Use them when editing command code, then run the required lint, test, and build checks.
Why use it?
They keep command changes local and reviewable while making sure related interface or architecture documents are updated when needed.

Command

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 commands/stackoverworld/primer-ai/agents
Clone the repo
git clone --depth 1 https://github.com/stackoverworld/primer-ai
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 150 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00150
Opus 5 $0.00000 $0.00075
Sonnet 5 $0.00000 $0.00030
Haiku 4.5 $0.00000 $0.00015

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

Security

Grade A, and why

AGENTS 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 yesterday.

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.

src/commands/AGENTS.md · 23 lines

What it actually says

AGENTS.md

Scope

  • Applies to: src/commands/**
  • Priority: this file overrides broader instructions for files in this subtree.

Focus

  • Command UX, validation, and error ergonomics.
  • Keep changes localized to this subtree unless a contract requires broader edits.
  • If API behavior changes, update docs/api-contracts.md.
  • If architecture boundaries change, update docs/architecture.md and ADRs.

Working Rules

  • Prefer small, reviewable patches.
  • Avoid hidden side effects across module boundaries.
  • Keep tests near the behavior they validate.
  • Do not skip verification commands.

Required Checks

  • npm run lint
  • npm run test
  • npm run build
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. yesterday First seen · 23 lines · 0 tokens per session scan A fde431619e54

Subscribe to this mod's changes

AGENTS is a command published in the GitHub repository stackoverworld/primer-ai (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 150 tokens. 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-31.