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 xobotyi/cc-foundry --skill siftgit clone --depth 1 https://github.com/xobotyi/cc-foundryWrote 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/xobotyi/cc-foundry/sift)<a href="https://agentmods.dev/skills/xobotyi/cc-foundry/sift"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/sift/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/xobotyi/cc-foundry/sift"><img src="https://agentmods.dev/badge/skills/xobotyi/cc-foundry/sift.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.00052 | $0.01143 |
| Opus 5.5 | $0.00021 | $0.00457 |
| Sonnet 5.5 | $0.00010 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
sift 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 2d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory holds facts that stay true after the session that wrote them; rules on how to work belong in a CLAUDE.md the user approved. An entry kept by mistake steers every later session, while one removed by mistake costs a rediscovery, so removal is the safe error. The user is present for this pass, and their answer is the evidence nothing else can give.
Where things are
- The memory directory is the path the auto-memory section of the system prompt names. better-memory keeps its data in a
sibling directory, never inside it: for
<dir>/memory/, the review file is<dir>/better-memory/review.md. That file holds instructions from entries written before better-memory, already moved out of memory and waiting for the user. - With
mcp__better-memory__remove_entryin the tool list, better-memory guards the directory. Remove an entry only with that tool, and save one only withmcp__better-memory__write_entry. Write, Edit, and shell commands that change the directory are refused, and better-memory writesMEMORY.mditself. - Without it, the entries are plain files.
MEMORY.mdis their index, one line per entry: delete an entry file and its line together.
Phase 1 — Inventory
Read every entry file, MEMORY.md, better-memory/review.md when it exists, and the instruction files in force: the
project's CLAUDE.md, .claude/CLAUDE.md, CLAUDE.local.md, its .claude/rules/ files, ~/.claude/CLAUDE.md, and
the ~/.claude/rules/ files.
Phase 2 — Judge
Give each entry one verdict:
- keep — a fact that still holds about the user, the project's situation, or an external system. A fact that names a file, path, command, version, or setting is checked against the project before it is kept: read the file, grep for the name, or run the command. A fact the project contradicts is removed.
- instruction — guidance on how to work: what to always or never do, a preference about the agent's behavior. It
becomes a CLAUDE.md line, never a memory entry. Every item in
review.mdis an instruction. - remove — progress of finished or current work, plans, a request for one task, a fact that no longer holds, and a duplicate of another entry or of an instruction file.
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.
- 2d ago First seen · 75 lines · 52 tokens per session scan A 2b2b7bbb082d
sift is a skill published in the GitHub repository xobotyi/cc-foundry (23 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,143 once invoked, about $0.0002 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-11-07.
sift compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| siftxobotyi/cc-foundry | Skill | 23 | yesterday | MIT | A | 52 | Claude Code |
| esp32-expertjohnkozaris/jko-claude-plugins | Skill | 11 | 4d ago | MIT | A | 137 | Claude Code |
| evolving-statusclaude-world/director-mode-lite | Skill | 80 | 19d ago | MIT | A | 17 | Claude Code |
| peekaboojohnkozaris/jko-claude-plugins | Skill | 11 | 4d ago | MIT | A | 104 | Claude Code |
| mobile-flows-maestrojohnkozaris/jko-claude-plugins | Skill | 11 | 4d ago | MIT | A | 102 | Claude Code |
| performance-auditgreglas75/zuvo | Skill | 7 | 6d ago | MIT | A | 90 | Claude Code |
| validate-mobilejohnkozaris/jko-claude-plugins | Skill | 11 | 4d ago | MIT | A | 20 | Claude Code |