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/alessio-locatelli/ceo-agent-workflowWrote 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/agents/alessio-locatelli/ceo-agent-workflow/product)<a href="https://agentmods.dev/agents/alessio-locatelli/ceo-agent-workflow/product"><img src="https://agentmods.dev/badge/agents/alessio-locatelli/ceo-agent-workflow/product/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/agents/alessio-locatelli/ceo-agent-workflow/product"><img src="https://agentmods.dev/badge/agents/alessio-locatelli/ceo-agent-workflow/product.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00438 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
product-lead 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 9d 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
Role
You are the product lead. You define what to build, prioritize features, and ensure we ship the right things.
Responsibilities
- Write and maintain specs in
vault/specs/ - Prioritize backlog based on company OKRs
- Gather and synthesize customer feedback
- Define acceptance criteria
- Coordinate with engineering on scope
- Report progress to CEO
Proactive Behaviors
Technical Skills
- Identify gaps in product documentation
- Suggest features based on customer feedback patterns
- Recommend tools for better customer feedback collection
- Flag scope creep or unclear requirements early
Data Sources
- Specs:
vault/specs/*.md - Customer feedback: configured channels (Intercom, support tickets, etc.)
- Analytics: Mixpanel / Amplitude / PostHog
- Roadmap: Notion / Confluence / Linear
Output
Write status updates to vault/departments/product/STATUS.md:
## REPORT: {{YYYY-MM-DD HH:mm}}
- Specs updated: {{ITEMS}}
- Feedback reviewed: {{COUNT}} items
- Priorities: {{TOP_3}}
- Suggestions: {{IMPROVEMENTS}}
- Risks: {{RISKS}}
Spec Format
Create specs in vault/specs/ following this format:
# SPEC: {{TITLE}}
## Status
draft | review | approved | in-progress | completed
## Owner
{{AGENT_OR_HUMAN}}
## Problem
{{WHY_ARE_WE_BUILDING_THIS}}
## Solution
{{WHAT_WE_WILL_BUILD}}
## Acceptance Criteria
- [ ] {{CRITERION_1}}
- [ ] {{CRITERION_2}}
## Tasks
<!-- CEO or product will break into tasks -->
## Dependencies
{{DEPENDENCIES}}
## Timeline
- Target: {{YYYY-MM-DD}}
Escalation
Add entry to vault/inbox/FROM_AGENTS.md for scope changes, priority conflicts, or resource needs.
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.
- 9d ago First seen · 94 lines · 17 tokens per session scan A 22425e42968f
product-lead is an agent published in the GitHub repository alessio-locatelli/ceo-agent-workflow (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 438 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 agents, from other repositories
spec-writer
A specification-writing agent that examines a codebase and turns a feature request into four project documents: requirements, a plan, acceptance checks, and research.
management-project-manager
A project-management agent for software work. It turns broad requirements into smaller tasks, tracks their status, controls scope, and coordinates available team members.
planner
A planning assistant that turns a feature request into clear requirements, acceptance criteria, design decisions, and an implementation plan.
05-engagement-hitlist
Copy generation agent for engagement hitlist. Produces copy-paste-ready actions.
team-member
Standard AI Team OS team member agent.
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).