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/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/plugins/aadarshvelu/syndicate/marketplace)<a href="https://agentmods.dev/plugins/aadarshvelu/syndicate/marketplace"><img src="https://agentmods.dev/badge/plugins/aadarshvelu/syndicate/marketplace/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/plugins/aadarshvelu/syndicate/marketplace"><img src="https://agentmods.dev/badge/plugins/aadarshvelu/syndicate/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
syndicate marketplace 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
{
"name": "syndicate",
"owner": {
"name": "Aadarsh velu",
"email": "[email protected]"
},
"plugins": [
{
"name": "syndicate-pipeline",
"source": {
"source": "url",
"url": "https://github.com/aadarshvelu/syndicate.git"
},
"description": "Run and diagnose the syndicate personal news digest pipeline from Claude Code.",
"version": "0.1.0",
"homepage": "https://github.com/aadarshvelu/syndicate",
"repository": "https://github.com/aadarshvelu/syndicate.git",
"license": "MIT",
"keywords": ["news", "rss", "newsletter", "digest", "pipeline", "twitter"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 23 lines scan A 82a4751d5ae2
syndicate marketplace is a plugin published in the GitHub repository aadarshvelu/syndicate (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
lid-experimental
Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
superstack
An agent-based software-development system that guides work from a short request to a tested, demonstrated piece of software. It uses checkpoints for planning and verification and explains conclusions in plain language.
great-pm
A full product team for a solo PM or founder. Specialist agents run the product loop — discovery, strategy, prioritization, specs, launch, measurement — while the human confirms a small number of gates.
adversarial-spec
Iteratively refine product specs through multi-model debate until consensus. Claude actively participates alongside GPT, Gemini, Grok, and other models. Includes interview mode, early agreement verification, and optional Telegram integration.
kb
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows.