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/AutomateLab-tech/agency-osWrote 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/automatelab-tech/agency-os/marketplace)<a href="https://agentmods.dev/plugins/automatelab-tech/agency-os/marketplace"><img src="https://agentmods.dev/badge/plugins/automatelab-tech/agency-os/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/automatelab-tech/agency-os/marketplace"><img src="https://agentmods.dev/badge/plugins/automatelab-tech/agency-os/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agency-os 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": "agency-os",
"version": "0.3.0",
"description": "Run your work like an AI agency, from a single Notion board.",
"url": "https://github.com/ratamaha-git/agency-os",
"author": "AutomateLab",
"license": "MIT"
}
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
2 files 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 · 9 lines scan A 6fb837e14c8a
agency-os marketplace is a plugin published in the GitHub repository AutomateLab-tech/agency-os (3 stars, last pushed 4mo 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
software-engineering
Subagent orchestration, wave execution, persistent completion, autonomous delivery, and migration batching.
spec-driven-development
Requirements clarification, phase planning, workstreams, and wave-based execution for reviewable delivery.
aidd-pm
Product backlog artifacts, refinement, Product Briefs, Epics, User Stories, Tasks, Spikes, Defects, requirements, and specs.
codebase-intelligence
Search-first codebase understanding, context retrieval, mapping, pattern detection, and living project intelligence.
connected-apps
Review-first runbooks for connected-app workflows and multi-system deployment sequencing.
data-engineering
Analytics engineering, dbt patterns, BigQuery optimization, data quality, and pipeline workflows.