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 agents/agricidaniel/sync/sync-secretarygit clone --depth 1 https://github.com/AgriciDaniel/syncWhat 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.00000 | $0.00771 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
sync-secretary 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 51 lines · 0 tokens per session scan A 9a01acdbe1d5
sync-secretary is an agent published in the GitHub repository AgriciDaniel/sync (18 stars, last pushed 9d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 771 tokens. 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-30.
Other agents, from other repositories
rondoflow-reviewer
Reviews a RondoFlow code change against this project's specific conventions and security rules (childprocess spawn safety, the { success, error } API envelope, per-user ownership/IDOR, Zod boundary validation, immutability, i18n parity, file/function size limits, Claude-auth handling). Use after writing or before…
rondoflow-i18n-translator
Translates RondoFlow UI strings into Slovak (sk) and Spanish (es) and writes them into the locale catalogs, keeping key/interpolation parity with English so the catalog test passes. Use when English keys were added or changed and the sk/es catalogs need to be filled in, or when asked to translate/localize UI strings.…
AGENTS
Agent "AGENTS" from fengzhizi715/OpenVitamin, covering agents.md — model agents governance, 1. 模块定位（module purpose）, 2. 设计边界（strict boundaries）, 2.1 model agent 必须做的事 ✅ and 2.2 model agent 严禁做的事 ❌.
ai-systems-architect
Use as the cross-cutting AI/systems DESIGN authority to decide WHERE a seam goes across the Rust core, Angular FE, and brain — provider/model abstraction, agentic tool-use loop bounds, tool/ACI design, the egress-consent-redaction-ledger firewall, routing, context assembly, a new ingest source or consumption surface.…
adversarial-verifier
Anti-false-positive verifier for Murmur. Use AFTER a change is written, to TRY TO BREAK it — run the real gates (cargo test --lib / ng build / ng lint), live-reproduce in a browser against the zoneless Angular app with a mocked Tauri IPC, and hunt for the failure modes this app has actually shipped (sealed-content…
app-perf-engineer
Use to diagnose or fix app-wide runtime performance across the Rust->IPC->Angular seam — startup latency, Tauri IPC throughput/heap (event vs Channel, un-windowed transcript payloads), OOM/RAM-pressure guards on DB/transcript/WAV allocations, Angular zoneless change-detection storms, O(n) template method bindings…