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/kousen/junie-training/agents-mdgit clone --depth 1 https://github.com/kousen/junie-trainingWrote 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/kousen/junie-training/agents-md)<a href="https://agentmods.dev/instructions/kousen/junie-training/agents-md"><img src="https://agentmods.dev/badge/instructions/kousen/junie-training/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 | $0.01253 | $0.01253 |
| Opus 5 | $0.00626 | $0.00626 |
| Sonnet 5 | $0.00251 | $0.00251 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
junie-training 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 4d 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:
- junie-training CLAUDE.md — 89% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Guidelines for Coding Agents
AGENTS.mdis the open, tool-agnostic guidance file read by Junie, Codex, and other coding agents. Keep it in sync withCLAUDE.md(which carries the same guidance for Claude Code). Edit both when project conventions change.
Project Context
This is a comprehensive Junie training repository for teaching JetBrains' AI coding agent across multiple IDEs, the Junie CLI, and CI/CD. The training materials were developed with AI assistance and demonstrate best practices for AI-assisted development.
Slide Presentation Best Practices
When creating or editing slides (especially in Slidev format):
One Idea Per Slide
- Each slide should contain ONE major concept
- Avoid the "bullet-riddled corpse" anti-pattern
- Better to have many simple slides than few dense ones
- ~30 focused slides work better than a dozen cramped ones
Content Guidelines
- Maximum 5-6 bullet points per slide
- Use progressive disclosure across multiple slides
- Keep code examples short and focused (5-10 lines max)
- Leave visual breathing room
Visual Design for Dark Mode
- Use high contrast colors for text on colored backgrounds
- Test all color combinations for readability
- Prefer lighter text shades (e.g.,
#dbeafeinstead of white on blue) - Add borders to colored boxes for definition
- Keep Mermaid diagrams simple to avoid parsing errors
Example Structure
---
## Single Concept Title
Key point or statement
Supporting detail if needed
---
Lab Instructions Format
When creating lab instructions:
Structure
- Learning Objectives - Clear, measurable goals
- Prerequisites - Tools and knowledge required
- Parts - Logical progression from simple to complex
- Tasks - Numbered, specific actions
- Expected Outcomes - What success looks like
- Common Issues - Troubleshooting section
- Challenge Extensions - Optional advanced tasks
- Reflection Questions - Reinforce learning
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.
- 4d ago First seen · 157 lines · 1,253 tokens per session scan A ff9db6eab92a
junie-training AGENTS.md is an instructions file published in the GitHub repository kousen/junie-training (11 stars, last pushed 1mo ago), licensed MIT. It adds 1,253 tokens to every session, about $0.0063 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
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).
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.
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.
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.
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).
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.