Borrowing it
Nothing to install: this file belongs to jnPiyush/AgentX. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jnPiyush/AgentX/master/AGENTS.mdgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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.
[](https://agentmods.dev/instructions/jnpiyush/agentx/agents-md)<a href="https://agentmods.dev/instructions/jnpiyush/agentx/agents-md"><img src="https://agentmods.dev/badge/instructions/jnpiyush/agentx/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.03423 | $0.03423 |
| Opus 5 | $0.01711 | $0.01711 |
| Sonnet 5 | $0.00685 | $0.00685 |
| Haiku 4.5 | $0.00342 | $0.00342 |
Grade C, and why
AgentX AGENTS.md scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Blocked commands: `rm -rf /`, `git reset --hard`, `drop database` How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Guidelines
Single source of truth for repository workflow guidance.
Map to all AgentX resources. For workflow details, see docs/WORKFLOW.md. For agent role definitions, see individual files in
.github/agents/.
Retrieval-Led Reasoning
IMPORTANT: Prefer retrieval-led reasoning over pre-training-led reasoning for ALL implementation tasks.
Always read_file the relevant SKILL.md, instruction file, or spec before generating code.
Do NOT rely on training data for project-specific patterns, conventions, or APIs.
If a skill, spec, or doc exists in the workspace, read it first; generate second.
Quick Reference
Issue-First Rule
Every piece of work SHOULD start with an issue. See docs/WORKFLOW.md for full flow.
# GitHub Mode
gh issue create --title "[Story] Add /health" --label "type:story" # Creates #42
git commit -m "feat: add health endpoint (#42)"
# Local Mode (issues optional by default)
git commit -m "feat: add user login"
Toggle enforcement: .agentx/agentx.ps1 config set enforceIssues true
Classification
| Type | Label | Route To |
|---|---|---|
| Broken? | type:bug |
Engineer |
| Research? | type:spike |
Architect |
| Docs only? | type:docs |
Engineer |
| Pipeline/deploy? | type:devops |
DevOps Engineer |
| ML/AI/eval? | type:data-science |
Data Scientist |
| Testing/cert? | type:testing |
Tester |
| Fabric data platform? | type:fabric |
Fabric Engineer |
| Power Platform solution? | type:lowcode |
Power Platform Builder |
| Power BI? | type:powerbi |
Power BI Analyst |
| Large/vague? | type:epic |
Product Manager |
| Single capability? | type:feature |
Architect |
| Otherwise | type:story |
Engineer |
Commit Format
type: description (#issue-number)
Types: feat, fix, docs, test, refactor, perf, chore
For final delivery in GitHub mode, plain (#123) is traceability only. Use fixes #123, closes #123, or resolves #123 in the final PR body or delivery commit so GitHub closes the issue automatically.
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 · 211 lines · 3,423 tokens per session scan C 47dc04d3d85e
AgentX AGENTS.md is an instructions file published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed today), licensed Apache-2.0. It adds 3,423 tokens to every session, about $0.0171 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.