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.
git clone --depth 1 https://github.com/rojim666/SztuCodeWrote 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/agents/rojim666/sztucode/memoryselector)<a href="https://agentmods.dev/agents/rojim666/sztucode/memoryselector"><img src="https://agentmods.dev/badge/agents/rojim666/sztucode/memoryselector/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/agents/rojim666/sztucode/memoryselector"><img src="https://agentmods.dev/badge/agents/rojim666/sztucode/memoryselector.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.00011 | $0.00024 |
| Opus 5.5 | $0.00004 | $0.00010 |
| Sonnet 5.5 | $0.00002 | $0.00005 |
| Haiku 4.5 | $0.00001 | $0.00002 |
Grade A, and why
memorySelector 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.
What it actually says
memory-selector-instructions
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 · 7 lines · 11 tokens per session scan A 97350fe724fa
memorySelector is an agent published in the GitHub repository rojim666/SztuCode (110 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 24 once invoked, about $0.0000 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-12.
Other agents, from other repositories
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
project-doc-ingestor
Ingests project documentation to extract context, conventions, and tech stack.
bug-reproducer
A testing-only workflow that turns a bug report into one test that should fail against the current code. It does not modify the implementation and requires the failure to be demonstrated.
scramjet:command-architect
Use when creating or substantially redesigning Scramjet commands or command sets.
forge-speccer-validator
Pre-planning path-validation gate. Scans a spec file for path tokens inside code fences or backticks, checks each against the target repo, and returns REPLANNEEDED with (spec-line, missing-path) pairs when any are missing. Invoked automatically by /forge plan before forge-planner.
forge-complexity
Analyzes task description and codebase context to recommend complexity depth level (quick/standard/thorough). Lightweight analysis run on every /forge command startup.