taOS AGENTS.md

Repository-specific instructions for the jaylfc/taOS project, including how to handle changelog fragments.

In plain words
What is it for?
They are for guiding work in that repository, especially changes that need corresponding changelog entries.
Why use it?
They give a coding agent project context and local rules that may not be obvious from the source code alone.

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/jaylfc/taos/agents-md
Clone the repo
git clone --depth 1 https://github.com/jaylfc/taOS

Made for: Codex, OpenCode.

Per session 136 This file is loaded in full into every session.
When invoked 136 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00136 $0.00136
Opus 5 $0.00068 $0.00068
Sonnet 5 $0.00027 $0.00027
Haiku 4.5 $0.00014 $0.00014

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

Security

Grade A, and why

taOS 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 · 12 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 12 lines · 136 tokens per session scan A 199b9fd82d7f

Subscribe to this mod's changes

taOS AGENTS.md is an instructions file published in the GitHub repository jaylfc/taOS (501 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 136 tokens to every session, about $0.0007 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.