opencode-froggy AGENTS.md

A set of project instructions for coding agents working on an OpenCode plugin written in TypeScript. It explains the folder layout, required Node.js version, and commands for building, checking, and testing the code.

In plain words
What is it for?
Use it when installing dependencies, building the plugin, checking types, running all tests, watching tests during development, or running one Vitest test file.
Why use it?
It gives an agent the project rules and exact commands needed to change the code without guessing how the repository works.

Instructions file for CodexOpenCode

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/smartfrog/opencode-froggy/agents-md
Clone the repo
git clone --depth 1 https://github.com/smartfrog/opencode-froggy

Made for: Codex, OpenCode.

Per session 1,125 This file is loaded in full into every session.
When invoked 1,125 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.01125 $0.01125
Opus 5 $0.00562 $0.00562
Sonnet 5 $0.00225 $0.00225
Haiku 4.5 $0.00112 $0.00112

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

Security

Grade A, and why

opencode-froggy 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 · 150 lines

How it starts

The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This repository is an OpenCode plugin written in TypeScript. The guidance below is for agentic coding tools that will modify or run code here.

Scope and structure

  • Source code lives in src/.
  • Tests live alongside sources in src/**/*.test.ts.
  • Build output goes to dist/.
  • Hooks configuration lives in hook/hooks.md (YAML frontmatter).
  • Agents, commands, and skills are loaded from agent/, command/, and skill/.
  • Skills are discovered by skill/<name>/SKILL.md.

Setup

  • Requires Node.js 18+.
  • Install dependencies with:
    • npm install

Build, typecheck, lint, test

There is no dedicated lint script or ESLint config. Use typecheck as the closest linting step.

  • Build:
    • npm run build
  • Typecheck (strict):
    • npm run typecheck
  • Tests (all):
    • npm test
  • Test watch (local dev):
    • npx vitest

Run a single test file

Vitest is configured via vitest.config.ts and runs src/**/*.test.ts.

Use any of the following:

  • npm test -- src/index.test.ts
  • npx vitest run src/index.test.ts

Run a single test by name

  • npm test -- -t "should parse valid frontmatter"
  • npx vitest run -t "should parse valid frontmatter"

Run a single test file and name

  • npx vitest run src/index.test.ts -t "should parse valid frontmatter"

Optional quick checks

  • Typecheck only:
    • npm run typecheck
  • Build only:
    • npm run build

Code style and conventions

TypeScript

  • Use TypeScript (ES module syntax) and keep strict type safety.
  • Avoid any. Prefer explicit types or narrow types with guards.
  • Prefer unknown for untrusted data, then validate or narrow.
  • Prefer Record<string, unknown> over loose object types.
  • Use type-only imports for types (import { type Foo } ...).

Imports

  • Use Node.js ESM imports, with node: specifiers for core modules:
    • import { join } from "node:path"
  • Prefer named imports; avoid default imports when not required.
  • Keep imports grouped and ordered:
    1. Node core modules
    2. External dependencies
    3. Local modules

Read the full file on GitHub · 150 lines

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 · 150 lines · 1,125 tokens per session scan A 1dda12be245d

Subscribe to this mod's changes

opencode-froggy AGENTS.md is an instructions file published in the GitHub repository smartfrog/opencode-froggy (105 stars, last pushed 3mo ago), licensed MIT. It adds 1,125 tokens to every session, about $0.0056 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.

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