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-summarizegit 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-summarize)<a href="https://agentmods.dev/skills/aadarshvelu/syndicate/syndicate-summarize"><img src="https://agentmods.dev/badge/skills/aadarshvelu/syndicate/syndicate-summarize.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.00031 | $0.00660 |
| Opus 5 | $0.00015 | $0.00330 |
| Sonnet 5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
syndicate-summarize 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-summarize
You are running the AI summarizer. This writes summary fields to the DB
and calls an LM (whichever provider AI_PROVIDER selects: ollama,
anthropic, openai, gemini, minimax). Cost-bearing — only run when
the user explicitly asked.
Step 1 — preflight
Run status and verify the provider matching env_present.AI_PROVIDER
(default ollama when unset) has its credential:
ollama→ollama_reachableistrueanthropic→env_present.ANTHROPIC_API_KEYistrueopenai→env_present.OPENAI_API_KEYistruegemini→env_present.GEMINI_API_KEYistrueminimax→env_present.MINIMAX_API_KEYistrue
If the provider can't be reached or the required key is missing, stop with a clear error rather than burning items on transient failures.
Also report items_unsummarized from status — that's the upper bound on
what this run could process.
Step 2 — summarize
Default --limit is 50. Parse $ARGUMENTS for --limit N:
cd "${SYNDICATE_REPO:-$(pwd)}" && uv run python -m pipeline.cli summarize --limit ${limit:-50}
Each item takes ~1–18 minutes depending on provider/model and whether the item has an image (vision items are slower). For local Ollama on a Mac M-series, plan ~2 minutes per item on average. The skill runs in a forked subagent context so progress logs are isolated.
Output envelope:
{"ok": true, "result": {"examined": N, "summarized": N, "skipped": N, "errors": []}, "log_path": "..."}
Step 3 — report
✓ summarize · examined=X done=Y skipped=Z
skipped includes items the summarizer classified as banter,
empty_content, or reaction (which have a skip_reason persisted so
they never re-process). Surface unexpected errors[] entries verbatim —
those are transient failures and will retry on the next run.
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 · 68 lines · 31 tokens per session scan A 4899c103204b
syndicate-summarize is a skill published in the GitHub repository aadarshvelu/syndicate (2 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 660 once invoked, about $0.0002 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
dspy-advanced-module-composition
Use for composing DSPy modules with Ensemble, MultiChainComparison, ensemble voting, sequential pipelines, and multi-program workflows.
dspy-optimize-anything
Use for GEPA optimizeanything on text artifacts such as code, prompts, agent architectures, configs, and non-DSPy optimization targets.
dspy-custom-module-design
Use for creating custom DSPy modules, extending dspy.Module, reusable components, stateful modules, serialization, and module testing.
dspy-evaluation-suite
Use for evaluating DSPy programs with Evaluate, answerexactmatch, SemanticF1, custom metrics, baselines, and program comparisons.
dspy-finetune-bootstrap
Use for BootstrapFinetune, fine-tuning DSPy models, teacher-student distillation, weight optimization, and lower-cost deployment.
dspy-gepa-reflective
Use for GEPA reflective optimization, ReAct agent optimization, feedback metrics, LLM reflection, and execution trajectories.