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 skills add lossless-group/lossless-agent-skills --skill maintain-filemapgit clone --depth 1 https://github.com/lossless-group/lossless-agent-skillsWrote 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/skills/lossless-group/lossless-agent-skills/maintain-filemap)<a href="https://agentmods.dev/skills/lossless-group/lossless-agent-skills/maintain-filemap"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/maintain-filemap/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/skills/lossless-group/lossless-agent-skills/maintain-filemap"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/maintain-filemap.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.00150 | $0.01780 |
| Opus 5.5 | $0.00060 | $0.00712 |
| Sonnet 5.5 | $0.00030 | $0.00356 |
| Haiku 4.5 | $0.00015 | $0.00178 |
Grade A, and why
maintain-filemap 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 1mo 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maintain-filemap · Loop
When the directory shape changes, regenerate the map. The committed
FILEMAP.mdat each repo root is the artifact a new collaborator opens first.
What this loop does
Keeps a FILEMAP.md at the root of each Lossless repo current with the actual on-disk tree. Each FILEMAP.md has two parts:
- A curator preface — hand-authored prose explaining what each top-level directory IS (purpose, ownership, conventions). Edited rarely (only when the meaning of a directory changes, not when its contents do).
- A generated tree — produced by
tree -L 3with a curated ignore set, spliced between<!-- TREE-START -->and<!-- TREE-END -->sentinels in a fenced code block. Regenerated by the loop's script every time the discipline fires.
Why both: a raw tree dump is useful but doesn't tell a newcomer what they're looking at. The curator preface is what makes the file legible; the generated tree is what makes it accurate.
When this loop fires
Three triggers:
| Trigger | Cadence | How it fires |
|---|---|---|
| Directory-shape change | as-it-happens | Pre-commit hook, OR manually as part of the commit that changes shape |
| Weekly cadence | every Monday | Manual or cron; produces a no-op commit if nothing changed |
| Pre-release | before each main/master ship |
Manual; bundled into the release commit |
The hook is optional but recommended. Without it, the discipline lives in the agent's working memory: "Did I just add corpus/? → regen FILEMAP."
What changes is a "directory-shape change"
Triggers the loop:
- A new top-level directory was added (
mkdir context-v/loops/) - A submodule was mounted or unmounted (
.gitmoduleschanged) - A major subsystem was renamed (
apps/dididecks-shell/→apps/deck-shell/) - A top-level file like
CLAUDE.mdorpnpm-workspace.yamlwas added - A new client-site landed under
client-sites/
Does NOT trigger the loop:
- A new file under an existing directory (e.g., adding
context-v/plans/Some-Plan.md) - A small refactor that doesn't change directory names
- A typo fix, dependency bump, or doc edit
- Adding a new variant under an existing client-site's
src/pages/scroll/{deck}/
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 121 lines · 150 tokens per session scan A 2b7cf6c8a749
maintain-filemap is a skill published in the GitHub repository lossless-group/lossless-agent-skills (4 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 1,780 once invoked, about $0.0006 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-08-31.
Other skills, from other repositories
code-sync
Reconcile the project's documents with what the code now shows, after a merge or at the end of a build: spec statuses (building → done only with a named gate, or → stale with the reason), assumed specs owed ratification, the project README map and its Last verified date. Surgical edits only. Use when the user says…
add
Process a document (PRD, architecture doc, security requirements, etc.) into structured context. Extracts relevant information and generates appropriate SCDs.
init
Initialize structured context for this project. Scaffolds .scs/ with all 11 concept bundles, scans the project, and recommends where to start.
validate
Check structure and surface issues for human review. Validates YAML, references, concept coverage, and compilation status.
status
Show what structured context exists and what's missing. Overview of bundles, SCDs, coverage across all 11 concepts, and compilation sync status.
use
Add known compliance or regulatory standards (HIPAA, SOC2, PCI, CHAI, GDPR) to your project context. Copies pre-built standards SCDs from the plugin's standards library.