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/jinexus-framework/jinexus-framework-skeleton/agents-mdgit clone --depth 1 https://github.com/jinexus-framework/jinexus-framework-skeletonWhat 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.01694 | $0.01694 |
| Opus 5 | $0.00847 | $0.00847 |
| Sonnet 5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
jinexus-framework-skeleton 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI coding agents (and humans) working in the jinexus-framework/jinexus-framework-skeleton package.
Read this before making changes.
What this package is
The official skeleton application for the JiNexus Framework. It provides a ready-to-go project structure for building MVC applications using the JiNexus Framework components (mvc, http, route, config, module-manager).
The skeleton wires up a single Application module that registers routes, controllers,
view templates, and error pages. It includes a PHP built-in server script for development,
a preconfigured PHPUnit test suite, and the full directory layout (config/, module/,
public/, data/, test/) expected by a JiNexus application.
Build & test commands
Run everything from the package root (the directory containing composer.json).
# Install dependencies
composer install
# Regenerate autoloader after adding/moving/renaming classes or namespaces
composer dump-autoload
# Run the full test suite (auto-discovers phpunit.dist.xml)
./vendor/bin/phpunit
# Equivalent via Composer scripts
composer test
composer test:coverage # sets XDEBUG_MODE=coverage and prints a text report
# Silence the local Xdebug "could not connect" notice
XDEBUG_MODE=off ./vendor/bin/phpunit
# Readable, per-test output
XDEBUG_MODE=off ./vendor/bin/phpunit --testdox
# Run a single file
XDEBUG_MODE=off ./vendor/bin/phpunit test/Application/ModuleTest.php
# Run a single test by name (regex against method names)
XDEBUG_MODE=off ./vendor/bin/phpunit --filter index_action_returns_a_view_model_with_hello_world
# Start the development server via Composer
composer run --timeout=0 serve
# Start the development server directly
php -S localhost:8000 -t public
There is no build step — this is a project skeleton consumed via composer create-project.
Project architecture
config/
application.config.php Module list for the application
modules.config.php Enabled module namespaces (e.g. 'Application')
module/
Application/
config/
module.config.php Route table + view-manager settings
src/
Module.php Application\Module — extends AbstractModule, returns config
Controller/
IndexController.php Application\Controller\IndexController — indexAction()
view/
application/
index/
index.phtml Default index view template
error/
404.phtml 404 error page
layout/
layout.phtml Master layout template
public/
index.php Front controller (entry point)
.htaccess Apache rewrite rules
asset/ Static assets (CSS, JS, images)
test/
Application/
ModuleTest.php Covers Module::VERSION and getConfig()
Controller/
IndexControllerTest.php Covers IndexController::indexAction()
Fixture/
ApplicationDouble.php Test double for ApplicationInterface
data/
cache/ Cache directory (writable at runtime)
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.
- 2d ago First seen · 160 lines · 1,694 tokens per session scan A 21a98d9fa8d0
jinexus-framework-skeleton AGENTS.md is an instructions file published in the GitHub repository jinexus-framework/jinexus-framework-skeleton (10 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 1,694 tokens to every session, about $0.0085 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
jesse AGENTS.md
Instructions for jesse-ai/jesse, covering jesse repository guide for ai agents, skills, key characteristics, central framework and technology stack.
laravel AGENTS.md
AGENTS.md instructions for laravel/laravel, covering laravel application, prerequisites and agent setup.
AgentEval copilot-instructions.md
Instructions for AgentEvalHQ/AgentEval, covering agenteval - ai coding agent instructions, architecture overview, environment setup, optional: secondary models for comparison and build & test commands.
LarAgent AGENTS.md
Instructions for MaestroError/LarAgent, covering purpose, key principles, planning, executing plan and testing.
AgentEval tracing.instructions.md
Guidelines for implementing trace recording and replay.
zhin zhin-plugin.instructions.md
Instructions for zhinjs/zhin, covering zhin plugin runtime authoring, package contract, convention directories, imports and native typescript and command routes.