trim-session-leakage SKILL.md skillA
trim-session-leakage from hamza-ali-shahjahan/hamzaish is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hamza-ali-shahjahan/hamzaish/trim-session-leakage@git:20260819.f995fd2Pins git:20260819.f995fd2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hamza-ali-shahjahan/hamzaish
- Path
factory/skills/trim-session-leakage/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260819.f995fd2, committed Aug 19, 2026
- Size
- 5,169 bytes
- Repository stars
- 10
- License
- MIT
Find and fix prose in a repo that only makes sense from inside the session that wrote it — dead references to a conversation, change narration ("used to", "no longer"), reviewer-addressed asides, and pointers to work that never landed. Use before a PR, before publishing docs, and when a repo has been written largely by agents. The test is one question - could a reader at HEAD, with no transcript, verify every claim?
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# trim-session-leakage — write from the repo's vantage, not the session's An agent writing prose has two vantages available and only one of them survives: - **the session** — what we just discussed, what the last attempt did, what a reviewer asked, what a later step will fix - **the repo at HEAD** — what a stranger can read, resolve, and verify today Prose written from the first vantage reads fine in the session that produced it and becomes unresolvable a week later. That's session leakage, and it's the characteristic decay of an agent-written codebase. **The one test.** For every sentence: > Could a reader at HEAD, with no access to any session transcript, PR thread, > or uncommitted draft, resolve every reference and verify every claim? If no, the sentence is written from the wrong vantage. Rewrite it to describe what is true now, or delete it. Method studied 2026-08-16 in `deepseek-ai/deepseek-harness` (`dsh-trim-cot-leakage`), which applies the same test across 688 agent-authored records. It is the natural mechanical companion to this repo's invariant that conversations never enter a repo: that rule keeps transcripts out, this skill keeps the *vantage* out. …
Read the whole file at its exact version.
How to install
mdr add hamza-ali-shahjahan/hamzaish/trim-session-leakage@sha256:93a1a403ddcd9a51The line at the top of this page pins the label git:20260819.f995fd2, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_yecqij7rlzlcd3a2)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 19, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5169 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hamza-ali-shahjahan/hamzaish · 10 stars · license MIT · pushed 2026-10-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yecqij7rlzlcd3a2 GET https://markdownregistry.com/api/v1/resolve?ref=hamza-ali-shahjahan/hamzaish/trim-session-leakage GET https://markdownregistry.com/api/v1/blob/93a1a403ddcd9a5166f168ff1fadceb7edfe7e81b79eb80ee2ab3ec7b73d7b51
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.