Borrowing it
Nothing to install: this file belongs to jonathan-vella/apex-accelerator. 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/jonathan-vella/apex-accelerator/main/.github/instructions/lesson-collection.instructions.mdgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/lesson-collection)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/lesson-collection"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/lesson-collection.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.00568 | $0.00568 |
| Opus 5 | $0.00284 | $0.00284 |
| Sonnet 5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
apex-accelerator lesson-collection.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 7d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lesson Collection Protocol
Orchestrators collect process observations during workflow execution and
generate 09-lessons-learned.json + 09-lessons-learned.md as workflow
completion artifacts (same pattern as 00-handoff.md and 00-session-state.json).
Initialization
At workflow start (when creating 00-session-state.json), also create:
// agent-output/{project}/09-lessons-learned.json
{
"workflow_mode": "production",
"project": "{project}",
"lessons": []
}
Set workflow_mode to "e2e" for the E2E Orchestrator.
When to Record a Lesson
Production Orchestrator Triggers
- Challenger review returns
must_fixfindings - User rejects an artifact and requests revision (log what was wrong)
- Subagent returns
NEEDS_REVISIONverdict - Deployment what-if reveals Azure Policy violations
- User explicitly flags an issue or concern during approval
E2E Orchestrator Triggers (superset of production)
All production triggers PLUS:
- Step needs >1 iteration (self-correction fired)
- Validator fails on first pass
- Pre-validation fails (agent returned empty/garbage)
bicep buildorterraform validatefails with hallucinated properties → categoryfactual-accuracy- Step exceeds timing threshold → category
workflow-design
Lesson Schema
Formal JSON Schema: tools/schemas/lesson-log.schema.json.
Required fields per entry: id, step, category,
severity, title, observation, root_cause, recommendation,
applies_to, applies_to_paths, status.
Completion Protocol
After the final workflow step completes (Step 7 for production, Phase H for E2E), generate the lessons-learned artifacts:
- Read
09-lessons-learned.json— the accumulated lesson entries - Generate
09-lessons-learned.mdnarrative using the H2 structure fromazure-artifacts/templates/09-lessons-learned.template.md - If zero lessons were captured, write a "clean run" summary: all steps passed without revision, no challenger must_fix findings
- Update
00-session-state.json— add09-lessons-learned.jsonand09-lessons-learned.mdto the artifacts list
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.
- 7d ago First seen · 67 lines · 568 tokens per session scan A 74454ff36e2a
apex-accelerator lesson-collection.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 5d ago), licensed MIT. It adds 568 tokens to every session, about $0.0028 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
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.