agentmods.dev

opencode-usage-plugin AGENTS.md

A set of repository instructions for an OpenCode usage-tracking plugin. It describes the TypeScript build checks, source directories, generated files, hook handlers, and provider logic.

In plain words
What is it for?
Use it to navigate the plugin, type-check and build it, understand where usage tracking and hooks are implemented, and follow its repository constraints.
Why use it?
It clarifies which files are authoritative and which files are generated or should be ignored. It also prevents unsafe workflows such as editing build output or starting blocking processes.

Instructions file for CodexOpenCode

24 6mo ago A scan 325 tokens original MIT
View the source file IgorWarzocha/opencode-usage-plugin
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/igorwarzocha/opencode-usage-plugin/agents-md
Clone the repo
git clone --depth 1 https://github.com/IgorWarzocha/opencode-usage-plugin

Made for: Codex, OpenCode.

Per session 325 This file is loaded in full into every session.
When invoked 325 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.00325 $0.00325
Opus 5 $0.00162 $0.00162
Sonnet 5 $0.00065 $0.00065
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

opencode-usage-plugin 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 · 36 lines

What it actually says

AGENTS.md - Usage Tracking Plugin

Dev Flow

  • tsc --noEmit - MUST use for type-checking before any commit.
  • npm run build - Compiles project to dist/.
  • ? RECOMMENDATION: Implement a one-shot test command (e.g., bun test or vitest).

Safety & Constraints

  • MUST NOT run long-running/blocking processes (dev servers, watch modes).
  • MUST NOT modify dist/ directly; it is generated by tsc.
  • MUST NOT modify package-lock.json unless changing dependencies.

Routing

  • Provider Logic: src/providers/ (See src/providers/AGENTS.md)
  • Plugin Entry: src/index.ts
  • Usage UI: src/ui.ts
  • Hook Handlers: src/hooks/

<context_hints>

  • src/types.ts - Shared schemas (UsageSnapshot, UsageEntry, PlanType).
  • src/state.ts - In-memory usage snapshot cache.
  • src/index.ts - Plugin entry point and hook registration.
  • Ignore: dist/, node_modules/, **/*.test.ts. </context_hints>
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 · 36 lines · 325 tokens per session scan A 810608115c34

Subscribe to this mod's changes

opencode-usage-plugin AGENTS.md is an instructions file published in the GitHub repository IgorWarzocha/opencode-usage-plugin (24 stars, last pushed 6mo ago), licensed MIT. It adds 325 tokens to every session, about $0.0016 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.

Languages
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens