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.
npx agentmods add instructions/rogermt/forgesyte/agents-mdgit clone --depth 1 https://github.com/rogermt/forgesyteWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.03629 | $0.03629 |
| Opus 5 | $0.01814 | $0.01814 |
| Sonnet 5 | $0.00726 | $0.00726 |
| Haiku 4.5 | $0.00363 | $0.00363 |
Grade A, and why
forgesyte 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 488 lines · 3,629 tokens per session scan A 1292af14e0ee
forgesyte AGENTS.md is an instructions file published in the GitHub repository rogermt/forgesyte (1 stars, last pushed 5mo ago), with no licence file. It adds 3,629 tokens to every session, about $0.0181 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.
Other instructions, from other repositories
AionUi AGENTS.md
AGENTS.md instructions for iOfficeAI/AionUi, covering aionui - project guide, code conventions, file & directory structure, naming and ui library & icons.
spec-kitty AGENTS.md
AGENTS.md instructions for Priivacy-ai/spec-kitty, covering spec kitty development guidelines, ⚠️ critical: load the project charter first, ⚠️ critical: template source location, ⚠️ critical: use canonical sources, never improvise and ⚠️ critical: git workflow — no direct pushes to origin/main.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
gemini-cli-desktop AGENTS.md
Instructions for Piebald-AI/gemini-cli-desktop, a project described as: Web/desktop UI for Gemini CLI/Qwen Code. Manage projects, switch between tools, search across past conversations, and manage MCP servers, all from one multilingual interface, locally or remotely.
sessionview AGENTS.md
Instructions for tyql688/sessionview, covering sessionview, commands, app / frontend, gates must pass under both feature sets: default (gui) and and --no-default-features --features headless.
SubFrame AGENTS.md
Instructions for Codename-11/SubFrame, covering subframe - subframe project, core working principle, relationship to native ai tools, session start and concurrent work & worktrees.