agentmods.dev

fps: Instructions file for Codex

AGENTS.md

fps AGENTS.md is an instructions file for Codex, OpenCode from mrcatnapper/fps. It costs 2,359 tokens per session, scanned B, original, MIT.

Project instructions for working on FPS, an experimental hidden network tunnel carried inside an existing secure web connection. They define the project’s specifications, documentation, work records, and version-control practices.

In plain words
What is it for?
Use them when modifying FPS code, documentation, work logs, or Git history.
Why use it?
They give coding agents the project context and rules needed to make changes consistently and safely.

Instructions file for CodexOpenCode

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

This is mrcatnapper/fps's own configuration. It tells Codex and OpenCode how to work on fps 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 fps configures →

not rated 10repo 4mo ago B scan 2,359 tokens original MIT
View source ↗ mrcatnapper/fps mrcatnapper.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to mrcatnapper/fps. 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/mrcatnapper/fps/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/mrcatnapper/fps

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 fps AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mrcatnapper/fps/agents-md/github.svg)](https://agentmods.dev/instructions/mrcatnapper/fps/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/mrcatnapper/fps/agents-md"><img src="https://agentmods.dev/badge/instructions/mrcatnapper/fps/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 fps AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/mrcatnapper/fps/agents-md"><img src="https://agentmods.dev/badge/instructions/mrcatnapper/fps/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,359 This file is loaded in full into every session.
When invoked 2,359 The same file — it is already loaded in full.
Security scan B 1 finding. 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.02359 $0.02359
Opus 5.5 $0.00944 $0.00944
Sonnet 5.5 $0.00472 $0.00472
Haiku 4.5 $0.00236 $0.00236

Measured 2mo ago against content hash 495de76df355, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

fps AGENTS.md scanned grade B with 1 finding 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 2mo 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

- Integration tests that require TUN/root/sudo must be clearly separated from
AGENTS.md · 217 lines

How it starts

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

AGENTS.md

Instructions for Codex/agents working on the FPS project in this workspace.

Scope: the whole repository from the directory that contains this file.

Project Context

  • The current main specification is ./docs/specification.md.
  • User/operator documentation lives in ./docs/.
  • Agent and developer working artifacts live in ./dev/ (WORKLOG.md, ROADMAP.md, NETWORK_RECOVERY.md, GitHub operations notes, fresh review briefs and similar files). The repository root should keep only this AGENTS.md and the short README.md.
  • FPS / Free Porn Storage is an experimental hidden L3 TUN tunnel carried over a live cover TLS session.
  • Before major changes, reread the specification and the current work log.

Version Control

  • Use Git as the source of truth for change history.
  • If the Git repository has not been initialized yet, initialize it at the workspace root before starting serious implementation work.
  • Commit changes regularly in small logical chunks.
  • Commit messages must be meaningful: state what changed and why.
  • Prefer local commits and local verification during normal development. Do not push every small edit just to trigger GitHub CI; use remote CI for review, release-candidate and integration checkpoints.
  • If a push is necessary for documentation-only or repository-hygiene changes that do not affect source code, tests, build files, Docker files or workflows, use a GitHub Actions skip marker such as [skip ci] in the commit message when branch policy allows it. Do not skip CI for source/runtime/config changes.
  • On develop and short-lived feature branches, squash, amend and --force-with-lease pushes are allowed when they make review history clearer and do not overwrite another person's work. Never force-push main.
  • To recover details, use git log, git show, git diff, git blame and the work log, not only the model's current context.
  • Check git status --short before starting work.
  • Do not revert changes made by the user or other agents unless explicitly asked.

Read the full file on GitHub · 217 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. 2mo ago First seen · 217 lines · 2,359 tokens per session scan B 495de76df355

Subscribe to this mod's changes

fps AGENTS.md is an instructions file published in the GitHub repository mrcatnapper/fps (10 stars, last pushed 4mo ago), licensed MIT. It adds 2,359 tokens to every session, about $0.0094 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project managementnetworking
Related

fps AGENTS.md compared with instructions from other repositories

fps AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
fps AGENTS.mdmrcatnapper/fpsInstructions file104mo agoMITB2,359Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode