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 aadarshvelu/syndicate --skill syndicate-notifygit clone --depth 1 https://github.com/aadarshvelu/syndicateWrote 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/aadarshvelu/syndicate/syndicate-notify)<a href="https://agentmods.dev/skills/aadarshvelu/syndicate/syndicate-notify"><img src="https://agentmods.dev/badge/skills/aadarshvelu/syndicate/syndicate-notify.svg" alt="Measured on agentmods" 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.00026 | $0.00422 |
| Opus 5 | $0.00013 | $0.00211 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
syndicate-notify 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 8d 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
/syndicate-notify
You are sending a Telegram message. External side-effect — only run when the user explicitly asked.
Step 1 — preflight
Run status and confirm env_present.TELEGRAM_BOT_TOKEN and
env_present.TELEGRAM_CHAT_ID are both true. If not, point the user at
the bot setup docs
and stop.
Step 2 — send
The notify subcommand reads an OrchestratorResult JSON from stdin. If the
user has a recent cli run output handy (e.g. from a prior session log
or a file they pass), pipe it in:
cd "${SYNDICATE_REPO:-$(pwd)}" && cat path/to/run-result.json | uv run python -m pipeline.cli notify
If the user just wants to re-send the LAST run summary without a stored
JSON, ask them to run /syndicate-run instead — that path notifies
automatically and is the canonical way to refresh the Telegram feed.
Output envelope:
{"ok": true, "result": {"ok": true}, "log_path": null}
Step 3 — report
One line: ✓ telegram notified on success, otherwise show the error.
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.
- 8d ago First seen · 47 lines · 26 tokens per session scan A 3e80035764b4
syndicate-notify is a skill published in the GitHub repository aadarshvelu/syndicate (2 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 422 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 skills, from other repositories
provider-integration
Adds new AI providers to claude-council, configures provider API settings, troubleshoots provider connections, and documents the provider script interface. Covers creating provider shell scripts, setting API keys, and validating connectivity. Triggers on "add provider", "new AI agent", "provider not working", "API…
update-lid
Configure or reconcile a project for linked-intent development (LID). Dispatches on project state — fresh bootstrap, append directives to an existing agent-instructions file (AGENTS.md or CLAUDE.md), add missing mode marker, reconcile convention drift, or run mode transitions. Invoked as /update-lid. For fresh…
map-codebase
Bootstrap LID in an existing (brownfield) codebase. Deep-reads every file in the declared scope, offers lens-based clustering options, generates skeleton LLDs/HLD/EARS bottom-up, then creates arrow docs and prompts the user to flesh out the skeletons. Token-intensive by design. Use when asked to map a codebase…
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
design
Create a doc-as-code design package from a PRD or SPEC. Conditionally generates C4 diagrams (Context/Container/Component), sequence diagrams, ER diagram + Data Dictionary, OpenAPI 3.0, AsyncAPI 3.0, ADRs, domain glossary, state diagrams, and deployment view as Mermaid-rendered Markdown files. Use when PM mentions…
recursive-decomposition
Handle tasks that exceed the context window by decomposing them: size and filter the input, chunk it, run recursive sub-agents on independent parts, verify on small windows, and synthesise programmatically, following the Recursive Language Models (RLM) research by Zhang, Kraska and Khattab (2025). Use when a task…