agentmods.dev

tempest AGENTS.md

A repository instruction file explaining how to work on tempest, a software factory that ships shared build workflows as portable AI-agent skills.

In plain words
What is it for?
Use it when modifying tempest, its skills, manifests, installer, scripts, or tests, especially before committing or pushing changes.
Why use it?
It gives coding agents and contributors the project’s structure, cross-agent compatibility rules, skill-writing conventions, and validation requirements in one place.

Instructions file for CodexOpenCode

2 2mo ago A scan 1,009 tokens original MIT
View the source file mtthsnc/tempest
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/mtthsnc/tempest/agents-md
Clone the repo
git clone --depth 1 https://github.com/mtthsnc/tempest

Made for: Codex, OpenCode.

Per session 1,009 This file is loaded in full into every session.
When invoked 1,009 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.01009 $0.01009
Opus 5 $0.00504 $0.00504
Sonnet 5 $0.00202 $0.00202
Haiku 4.5 $0.00101 $0.00101

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

Security

Grade A, and why

tempest 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 · 69 lines

How it starts

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

AGENTS.md

Guidance for coding agents (and humans) working on the tempest repo. For what it does and how to install it, see README.md; for the cross-harness design, see docs/ARCHITECTURE.md.

What this repo is

tempest is a software factory: a set of opinionated build workflows — plan → build → review → test → ship → reflect — shipped as portable Agent Skills that run identically on Claude Code and pi. The skills are the product; the manifests and installer are thin wiring around one shared source tree. It contains no personal data.

Golden rules

  1. One source, two harnesses. Every skill is authored once under plugins/tempest/skills/<name>/SKILL.md following the Agent Skills standard. Never fork a skill per harness. If a harness needs something different, express it in the install wiring, not in duplicated content.
  2. The conformance gate is law. ./scripts/validate.sh must pass before any commit; ./tests/run.sh before any push. CI runs both.
  3. Skill description = trigger, not summary. Start every skill description with "Use when…" and describe when to invoke, never the workflow. A description that summarizes the steps makes agents follow the summary instead of reading the skill body. (The gate enforces the "Use when" prefix.)
  4. Commands are portable or they don't ship. A commands/<verb>.md must use only the arg subset both harnesses share ($ARGUMENTS, $1–$9) and carry a description. Pi-only (${1:-def}, ${@:N}) and Claude-only (allowed-tools, model) syntax is flagged by the gate.
  5. No hardcoded user, home, or project paths. Default to ~/.claude/…, ~/.pi/…, ~/.agents/… (resolve per user) or read from settings. A grep for /home/ in tracked files returns nothing.

Layout

.claude-plugin/marketplace.json        Claude marketplace index (lists the plugin)
plugins/tempest/
  .claude-plugin/plugin.json           Claude plugin manifest
  skills/<name>/SKILL.md               THE skills (Agent Skills standard) — author once
  commands/<verb>.md                   thin slash entry points (also pi prompt templates)
package.json                           pi package manifest (pi.skills / pi.prompts)
AGENTS.md  CLAUDE.md -> AGENTS.md       instructions (Claude reads CLAUDE.md; pi reads either)
install.sh  uninstall.sh               idempotent wiring into ~/.agents, ~/.claude, ~/.pi
scripts/validate.sh                    conformance gate
tests/run.sh                           sandbox install + manifest/skill assertions
docs/ARCHITECTURE.md                   the cross-harness design

Read the full file on GitHub · 69 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 · 69 lines · 1,009 tokens per session scan A 18604909736d

Subscribe to this mod's changes

tempest AGENTS.md is an instructions file published in the GitHub repository mtthsnc/tempest (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,009 tokens to every session, about $0.0050 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-31.

Testingagent-skillsai-agentsclaude-codedeveloper-toolspisoftware-factory
Related

Other instructions, from other repositories

pi-subagents AGENTS.md

Instructions for tintinweb/pi-subagents, covering development rules, conversational style, code quality, documentation and commands.

tintinweb/pi-subagents · 2,696 tokens

Accordion CLAUDE.md

Instructions for a-Fig/Accordion, covering claude.md — accordion, key urls, terminology, codebase map and engine — single source of truth.

a-Fig/Accordion · 13,772 tokens

pi-anthropic-auth AGENTS.md

Instructions for gotgenes/pi-anthropic-auth, covering agents guide: pi-anthropic-auth, project, primary goal, current status and principles.

gotgenes/pi-anthropic-auth · 6,534 tokens

Accordion AGENTS.md

Instructions for a-Fig/Accordion, a project described as: 🏆 AI Hackathon 2026 @ UC Berkeley Intelligent context management for developers.

a-Fig/Accordion · 391 tokens

har AGENTS.md

Instructions for os-factory/har, covering har — agent development guide, har / agent environment, harnesses in this repo, harness workflow (dogfooding) and run history.

os-factory/har · 4,798 tokens

pi-codex-goal AGENTS.md

Instructions for fitchmultz/pi-codex-goal, covering pi-codex-goal — agent notes, local pi install policy, verify before finishing and layout.

fitchmultz/pi-codex-goal · 637 tokens