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/phenixphp/framework/phenixgit clone --depth 1 https://github.com/phenixphp/frameworkWhat 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.00413 | $0.00413 |
| Opus 5 | $0.00206 | $0.00206 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
framework phenix.instructions.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 today.
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.
What it actually says
Coding standards, domain knowledge, and preferences that AI should follow.
- Use clear and descriptive variable names.
- Follow the PSR-12 coding style guide.
- Write unit tests for all new features and bug fixes.
- Keep functions and methods small and focused on a single task.
- Use type hints and return types for all functions and methods.
- Avoid using global variables.
- Use dependency injection instead of singletons.
- Write code that is easy to read and understand.
- Keep the codebase organized and modular.
Context
- This project is a framework to build API applications.
- The primary language used is PHP.
- This framework is based on Amphp version 3, a high-performance asynchronous PHP framework.
- The application uses a MySQL, PostgreSQL, and SQLite database for data storage.
- The application uses Redis for caching.
- The application uses PestPHP for unit testing.
- The application uses Composer for dependency management.
Paths
- Application code is located in the
srcdirectory. - Tests are located in the
testsdirectory.
Framework components
- Crypto:
src/Crypto - Database:
src/Database - Query Builder:
src/Database/QueryBuilder - Filesystem:
src/Filesystem - Logging:
src/Logging - Mail:
src/Mail - Queue:
src/Queue - Routing:
src/Routing - Session:
src/Session - Tasks:
src/Tasks - Validation:
src/Validation - Views:
src/Views
Current feature under development
- The current feature under development is the
src/Queuecomponent, which provides a unified API for managing background tasks processing. - The
src/Queueuses queuable tasksrc/Queue/QueuableTaskfor defining tasks that can be processed in the background. - The
src/Queuecomponent supports multiple queue drivers, including redis, database, and parallel.
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.
- today First seen · 50 lines · 413 tokens per session scan A 7c874afc5075
framework phenix.instructions.md is an instructions file published in the GitHub repository phenixphp/framework (13 stars, last pushed 2mo ago), licensed MIT. It adds 413 tokens to every session, about $0.0021 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-09-02.
Other instructions, from other repositories
the-seo-framework copilot-instructions.md
Copilot instructions for sybrew/the-seo-framework, covering repository-specific rules, repository-specific work types, file management, response style and general operating rules.
the-seo-framework php.instructions.md
Use when editing PHP, WordPress PHP, SQL-in-PHP, or mixed PHP and HTML template files in this repository. Covers TSF PHP style, namespace rules, SQL formatting, and template formatting.
the-seo-framework docs.instructions.md
Use when editing README.md, readme.txt, or other user-facing documentation for this repository. Covers readme wording constraints, WordPress readme format, changelog prose style, and public API naming requirements.
the-seo-framework local.instructions.md
Use when handling local-only workspace guidance, private support materials, related-repository cross-references, remediation, troubleshooting, reproduction, triage, or customer-facing diagnosis that may require code changes.
the-seo-framework javascript.instructions.md
Use when editing JavaScript files in this repository. Covers TSF JavaScript syntax and formatting expectations.
the-seo-framework css.instructions.md
Use when editing CSS files in this repository. Covers TSF stylesheet conventions and layout-debugging expectations.