Borrowing it
Nothing to install: this file belongs to rjmurillo/ai-agents. 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/rjmurillo/ai-agents/main/.github/instructions/session-logs.instructions.mdgit clone --depth 1 https://github.com/rjmurillo/ai-agentsWrote 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/rjmurillo/ai-agents/session-logs)<a href="https://agentmods.dev/instructions/rjmurillo/ai-agents/session-logs"><img src="https://agentmods.dev/badge/instructions/rjmurillo/ai-agents/session-logs/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/instructions/rjmurillo/ai-agents/session-logs"><img src="https://agentmods.dev/badge/instructions/rjmurillo/ai-agents/session-logs.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.01014 | $0.01014 |
| Opus 5.5 | $0.00406 | $0.00406 |
| Sonnet 5.5 | $0.00203 | $0.00203 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
ai-agents session-logs.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 28d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Log Mechanics
.agents/schemas/session-log.schema.json describes what a session log
contains. Session log creation is discontinued: do not create a new
.project-toolkit/sessions/*.json file. Nothing ever required one to commit, push, or
open a PR. The existing logs under .project-toolkit/sessions/ stay in the repository
as history and remain readable by the retrospective skill, memory
extraction, and the PreCompact hook. This rule covers the mechanics that still
apply to a log that already exists on your branch (carried over from before
this change, or cherry-picked from an older one).
Scoped to .agents/** rather than ** on purpose. The mechanics matter only
when a change touches that tree. The generator skips this rule from consumers
that do not retain internal .agents/** paths. Issue #4317 tracks that
destination-dependent behavior.
MUST
-
Do not create a new session log. Session log creation is discontinued; no start, end, commit, push, or PR gate ever required one, and none does now. If a log named
.project-toolkit/sessions/YYYY-MM-DD-session-NN<slug>.jsonends up staged anyway (for example, cherry-picked from an older branch), thesession-policypre-commit hook still validates it (scripts/validation/git_hook_policy.py session, a validate-if-present gate): a malformed log still blocks that commit. When no log is staged, the gate returns 0 (check_sessionspasses when there are no session paths, and also when_merge_in_progress). -
Record
endingCommitin a follow-up commit, never by amending. Amending replaces the commit whose SHA the log names, sovalidate_session_json.pythen reports the recorded SHA as unreachable (issue #3618). Commit the work withendingCommitempty, then commit the SHA in a second commit. The reachability check returns no finding in a shallow clone (session_scope.pyshort-circuits when--is-shallow-repositoryis true), so a green CI run on a shallow checkout is not evidence the SHA is reachable.
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.
- 28d ago Changed · +11 tokens per session 2b554b2e2fb4
- 1mo ago Changed · -3 lines · -66 tokens per session 1544e459fc82
- 1mo ago First seen · 77 lines · 1,069 tokens per session scan A d96d4f5cc14a
ai-agents session-logs.instructions.md is an instructions file published in the GitHub repository rjmurillo/ai-agents (48 stars, last pushed today), licensed MIT. It adds 1,014 tokens to every session, about $0.0041 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-09-03.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.