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/alirezarezvani/claude-cto-teamWrote 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/alirezarezvani/claude-cto-team/marketplace)<a href="https://agentmods.dev/plugins/alirezarezvani/claude-cto-team/marketplace"><img src="https://agentmods.dev/badge/plugins/alirezarezvani/claude-cto-team/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/alirezarezvani/claude-cto-team/marketplace"><img src="https://agentmods.dev/badge/plugins/alirezarezvani/claude-cto-team/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
cto-team-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": "cto-team-marketplace",
"owner": {
"name": "Alireza Rezvani",
"email": "[email protected]"
},
"plugins": [
{
"name": "cto-team",
"source": {
"source": "github",
"repo": "alirezarezvani/claude-cto-team"
},
"description": "Strategic CTO advisory team with specialized agents for architecture design, plan validation, and technology decisions",
"version": "1.0.0",
"author": {
"name": "Alireza Rezvani",
"url": "https://github.com/alirezarezvani"
},
"homepage": "https://github.com/alirezarezvani/claude-cto-team",
"repository": "https://github.com/alirezarezvani/claude-cto-team",
"license": "MIT",
"keywords": [
"cto",
"architecture",
"strategic-planning",
"tech-decisions",
"validation",
"roadmap",
"build-vs-buy",
"system-design",
"ml-architecture"
],
"category": "productivity"
}
]
}
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 · 38 lines scan A 40e313b23cc1
cto-team-marketplace is a plugin published in the GitHub repository alirezarezvani/claude-cto-team (119 stars, last pushed 10mo 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-30.
Other plugins, from other repositories
c-level-agents
Founder-mode executive team plugin: 13 cs- C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff, General Counsel, Chief Data Officer, Chief AI Officer, Chief Customer Officer, VP of Engineering) plus 21 /c-level-agents: slash commands for forcing-question office hours (incl. /c-level-agents:vpe-review).
section-508
Expert Section 508 compliance advisor for US federal ICT accessibility — VPAT/ACR completion, WCAG 2.0 AA audits, remediation planning, PDF accessibility, procurement language, keyboard and screen reader testing, undue burden assessments, and agency compliance workflows.
executive-assistant
Triage inboxes, prep meetings, and draft follow-ups that keep executives moving.
repo-doctor
Diagnostic skills for GitHub repos. Currently ships readme-doctor — a structured review of a repo's README against best-practice patterns (hero presence, install-to-first-success length, audience match, drift signals), output as a prioritized punch list.
spec-first marketplace
Spec-first development: define a spec, implement it, and generate docs.
contexture-lite
Smaller contexture for local or small-context models: the rules, memory, review, and debugging skills only.