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/jnpiyush/agentx/pythongit clone --depth 1 https://github.com/jnPiyush/AgentXWhat 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.00363 | $0.00363 |
| Opus 5 | $0.00181 | $0.00181 |
| Sonnet 5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
AgentX python.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 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.
What it actually says
Python Instructions
Auto-loads when editing Python files. For comprehensive standards, load the skill.
Skill: .github/skills/languages/python/SKILL.md
Key Rules
- Follow PEP 8 style guide
- Use type hints for all function signatures (PEP 484)
- Maximum line length: 88 characters (Black formatter)
- Use
rufffor linting and formatting - Google style docstrings
- Catch specific exceptions, never bare
except: - pytest for testing, pytest-asyncio for async
- Name tests:
test_function_name_scenario_expected
Critical Rules (Embedded -- Always Active)
Security
- Validate/sanitize ALL inputs at API boundaries
- Parameterize SQL via ORM or
cursor.execute(sql, params)-- NEVER f-strings or.format() - Secrets in env vars (
os.environ) or Key Vault -- NEVER hardcode - Use
secrets.compare_digest()for constant-time comparisons
Testing
- 80%+ code coverage required (
pytest --cov) - Pyramid: 70% unit, 20% integration, 10% e2e
- AAA pattern (Arrange-Act-Assert) in every test
- No bare
assert True-- assert specific values
Error Handling
- Catch specific exceptions (
ValueError,KeyError, etc.) - Log with context:
logger.error("msg", extra={"agent": ..., "issue": ...}) - Retry transient failures with exponential backoff (
tenacity) - Fail fast on invalid input at module boundaries
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 · 43 lines · 363 tokens per session scan A 5af236a0a001
AgentX python.instructions.md is an instructions file published in the GitHub repository jnPiyush/AgentX (15 stars, last pushed 5d ago), licensed Apache-2.0. It adds 363 tokens to every session, about $0.0018 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-30.
Other instructions, from other repositories
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.
buildNext
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
spec-kit 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.
langchain 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.