output: Instructions file for Codex

AGENTS.md

output AGENTS.md is an instructions file for Codex, OpenCode from growthxai/output. It costs 491 tokens per session, scanned B, original, Apache-2.0.

Repository instructions for working on Output.ai, a framework for building workflows and software agents. They explain the project structure, documentation locations, package commands, and how to verify changes in its pnpm workspace monorepo, which is a repository containing multiple related packages.

In plain words
What is it for?
Use them when changing Output.ai code, documentation, CLI templates, or coding-agent plugin documentation.
Why use it?
They prevent contributors from using the wrong commands or ignoring project-specific rules, especially when editing shared packages or generated project templates.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is growthxai/output's own configuration. It tells Codex and OpenCode how to work on output itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything output configures →

Reuse

Borrowing it

Nothing to install: this file belongs to growthxai/output. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/growthxai/output/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/growthxai/output

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for output AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/growthxai/output/agents-md/github.svg)](https://agentmods.dev/instructions/growthxai/output/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/growthxai/output/agents-md"><img src="https://agentmods.dev/badge/instructions/growthxai/output/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for output AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/growthxai/output/agents-md"><img src="https://agentmods.dev/badge/instructions/growthxai/output/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 491 This file is loaded in full into every session.
When invoked 491 The same file — it is already loaded in full.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00491 $0.00491
Opus 5.5 $0.00196 $0.00196
Sonnet 5.5 $0.00098 $0.00098
Haiku 4.5 $0.00049 $0.00049

Measured 6d ago against content hash 8d586a898455, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

output AGENTS.md scanned grade B with 2 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 6d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

`curl -X POST http://localhost:3001/workflow/run -H "Content-Type: application/json" -d '{"workflowName": "simple", "input": {"values": [1, 2, 3, 4, 5]}}'`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

`curl -X POST http://localhost:3001/workflow/run -H "Content-Type: application/json" -d '{"workflowName": "simple", "input": {"values": [1, 2, 3, 4, 5]}}'`
AGENTS.md · 32 lines

How it starts

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

AGENTS.md

This file provides guidance to coding agents when working with the Output.ai (often referred as just Output) framework codebase.

Project Overview

Output.ai is an AI framework for building reliable production-ready LLM workflows & agents. It contains multiple NPM packages and supporting infrastructure with best AI engineering practices baked-in. Under the hood, the Output framework uses Temporal.io as the execution layer.

Product documentation lives in docs/guides/ (packages under docs/guides/packages/). Use it as the reference for public behavior.

Package Management

This monorepo uses pnpm workspaces with a pnpm-workspace.yaml and pnpm-lock.yaml.

Note: the pnpm convention applies to this monorepo only. Projects generated by output init are npm-based - sdk/cli/src/templates/project/package.json.template ships npm scripts (output:worker:build, output:worker:watch, output:dev). When editing CLI templates or the coding_assistants/ plugin docs, write the template's npm commands, not monorepo-only ones like pnpm run build:packages.

When Working on This Project

  1. Always base your code on existing code patterns and project hierarchical organization.
  2. When developing test workflows, use the existing workflows in test_workflows/ as reference.
  3. Maintain TypeScript definitions alongside JavaScript implementations.
  4. Prefer a functional approach over an object-oriented approach; avoid classes/inheritance unless absolutely necessary.
  5. DO NOT opt out of linting rules or change the linting rules unless specifically requested by the user.
  6. Always ask the user if they would like to update the documentation after any new changes.

How to confirm you've made changes successfully

  • Full CI-equivalent check (install, lint, build, tests, docs in Docker): ./run.sh validate
  • Targeted tests: pnpm test <paths>
  • Running system: ./run.sh dev, then from a separate terminal: curl -X POST http://localhost:3001/workflow/run -H "Content-Type: application/json" -d '{"workflowName": "simple", "input": {"values": [1, 2, 3, 4, 5]}}'

Read the full file on GitHub · 32 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. 6d ago First seen · 32 lines · 491 tokens per session scan B 8d586a898455

Subscribe to this mod's changes

output AGENTS.md is an instructions file published in the GitHub repository growthxai/output (443 stars, last pushed yesterday), licensed Apache-2.0. It adds 491 tokens to every session, about $0.0020 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-10.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

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 · 9,649 tokens

next.js AGENTS.md

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,257 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

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,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens