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 agentmods add commands/alpayc/abfall-mcp-server/update-datagit clone --depth 1 https://github.com/AlpayC/abfall-mcp-serverWhat 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 | $0.00011 | $0.00361 |
| Opus 5 | $0.00005 | $0.00180 |
| Sonnet 5 | $0.00002 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
update-data 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.
What it actually says
Bring the vendored hacs_waste_collection_schedule up to date and rebuild the
registry. Both must move together — data/providers.json is generated from the
submodule, and CI fails if they disagree.
-
Record the current provider count and submodule commit:
git submodule status vendor/hacs_waste_collection_schedule uv run python -c "import json; print(json.load(open('data/providers.json', encoding='utf-8'))['count'])" -
Update the submodule and rebuild:
git submodule update --remote --depth 1 vendor/hacs_waste_collection_schedule uv run python scripts/build_registry.py -
Run the suite. Upstream occasionally renames a source module or changes an argument signature, which surfaces here:
uv run ruff check src scripts tests && uv run pytest -
Report:
- provider count before → after, and the new submodule commit
- whether tests pass
- a drop in the provider count needs an explanation before this is
committed: either something was removed upstream, or the country
assignment in
scripts/build_registry.pystopped matching. Check the README section parsing (readme_modules) if the drop is large.
Stage vendor/ and data/providers.json in the same commit. Do not commit
unless asked.
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 · 41 lines · 11 tokens per session scan A d9bd53b8687e
update-data is a command published in the GitHub repository AlpayC/abfall-mcp-server (1 stars, last pushed 5d ago), licensed MIT. It adds 11 tokens to every session and 361 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
flow-nexus-neural
Train and deploy neural networks in distributed sandboxes.
flow-nexus-auth
Flow Nexus authentication and user management.
editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.
add-tool
Scaffold a new FreeAgent MCP tool (handler + registration + test) following the repo pattern.
OPSX: Archive
Archive a completed change in the experimental workflow.
session-start
Invoke at the BEGINNING of every working session. Token budget: 500–1,500. -->.