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.
git 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/rules/jnpiyush/agentx/000-agentx-core)<a href="https://agentmods.dev/rules/jnpiyush/agentx/000-agentx-core"><img src="https://agentmods.dev/badge/rules/jnpiyush/agentx/000-agentx-core/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/jnpiyush/agentx/000-agentx-core"><img src="https://agentmods.dev/badge/rules/jnpiyush/agentx/000-agentx-core.svg" alt="Reviewed on agentmods" width="80" 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.00561 | $0.00561 |
| Opus 5.5 | $0.00224 | $0.00224 |
| Sonnet 5.5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
000-agentx-core 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 2mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- 000-frontier-core — 94% identical, 88 lines differ
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentX Core Contract (Cursor)
This workspace runs AgentX. Cursor operates in CLI-backed mode: agent definitions, skills, and templates are read in place from the repo. Prefer retrieval-led reasoning -- read the canonical file before generating.
Canonical Sources (read these, do not duplicate)
- Routing + rules map:
AGENTS.md - Cross-cutting agent protocol:
.github/AGENT-PROTOCOL.md - Workflow + handoffs:
docs/WORKFLOW.md - Skills index (load on demand):
Skills.md - Agent role contracts:
.github/agents/*.agent.md
Quality Loop (NON-SKIPPABLE)
Before editing, creating, or deleting any file for a code or docs change, run
.agentx/agentx.ps1 loop start -p "<task>" as the FIRST action. The loop is not
done until .agentx/agentx.ps1 loop complete -s "<summary>" succeeds, with at
least 5 iterations and a structured reviewer verdict recorded on the final work
iteration:
loop iterate -s "Subagent Review: <outcome>" -e <evidence> --verdict approved --reviewer <id> --high 0 --medium 0. A summary containing the word "review" no
longer satisfies the gate. When the AgentX MCP server is registered
(.cursor/mcp.json), use the agentx_loop_* tools instead of typing the CLI --
agentx_loop_iterate accepts the same verdict, reviewer, high and medium fields.
The pre-commit hook blocks commits that violate the loop gate.
Workflow Gates
- Compound Capture, Model Council (ADR/PRD/eval), Execution Plan (>= 8 code
files), and Brainstorm gates apply per
.github/AGENT-PROTOCOL.md. - Scrub before handoff:
.agentx/agentx.ps1 scrub -Path <changed-area>. - Karpathy guidelines apply to every change.
Conventions
- Commit format:
type: description (#issue)-- feat, fix, docs, test, refactor, perf, chore. - ASCII-only: use
->not arrows,-not em-dashes,[PASS]/[FAIL]. - Create deliverables locally; never push files straight to the remote.
Commands
Role workflows are available as .cursor/commands/*.md, each a thin wrapper over
.github/agents/<role>.agent.md. Invoke the matching command, then read that
canonical agent file before acting.
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.
- 2mo ago First seen · 53 lines · 561 tokens per session scan A ea60230fe60a
000-agentx-core is a cursor rule published in the GitHub repository jnPiyush/AgentX (18 stars, last pushed 4d ago), licensed Apache-2.0. It adds 561 tokens to every session, about $0.0022 per session on Opus 5.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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).