Home / ppgranger / token-saver · src/processors/AGENTS.md · GitHub

AGENTS.md@src/processors agentsA

Name: AGENTS.md@src/processors
Author: ppgranger

AGENTS.md@src/processors is agent-read markdown (agents) from ppgranger/token-saver.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# Processor contract

- Follow the root Google Python style policy. Import `from src.processors import
  base` and subclass `base.Processor`; describe supported output and preservation
  limits in docstrings. Use explicit loops for multi-stage parsing instead of
  comprehensions with multiple `for` clauses.
- Implement a concrete `Processor` with a stable `name`, numeric `priority`,
  anchored `hook_patterns`, `can_handle(command)`, and `process(command, output)`.
  Discovery and hook-pattern collection are automatic; do not add a second
  manual registry. Equal priorities are ordered by name.
- Keep hook patterns and routing predicates aligned. A processor should not
  intercept unrelated command names, filename substrings, or flags belonging
  to another tool. Test positive and negative matches and launcher variants.
- Respect priority ranges in `base.py`; `999` belongs to the generic fallback.
  Choose lower priority numbers only when a tested routing override requires it.
- Return the original text for empty, short, dense, or unrecognized shapes when
  no safe transformation exists. Do not invent a success summary from ambiguous
…

Read the whole file at its exact version.

How to install

Latest version

mdr add ppgranger/token-saver/src/processors/AGENTS.md@git:20260919.8bd664b

Exact content

mdr add ppgranger/token-saver/src/processors/AGENTS.md@sha256:50cf9cac86955688

Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.

Badge

[![mdr](https://markdownregistry.com/badge/art_nmwef5jkwbouwlbz.svg)](https://markdownregistry.com/a/art_nmwef5jkwbouwlbz)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260919.8bd664b latest	2026-09-19	8bd664b	2,284 B	A	view

Audit of the latest version

A 14 of 14 checks passed. Deterministic, no model, same answer every run.

pass: Size between 200 bytes and 200 KB (2284 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

GitHub

ppgranger/token-saver · 153 stars · license Apache-2.0 · pushed 2026-09-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_nmwef5jkwbouwlbz
GET https://markdownregistry.com/api/v1/resolve?ref=ppgranger/token-saver/src/processors/AGENTS.md
GET https://markdownregistry.com/api/v1/blob/50cf9cac869556884665ebb1db959b25d9cb030a739fe710f61f84c4e6ab8891

Your agent 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.