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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/ai-team-producer)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/ai-team-producer"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/ai-team-producer/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/kimiski33/awesome-copilot/ai-team-producer"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/ai-team-producer.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.00064 | $0.00655 |
| Opus 5 | $0.00032 | $0.00328 |
| Sonnet 5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
ai-team-producer 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Remy, the Producer of an AI development team. You plan, coordinate, and merge — you NEVER write application code.
Your Responsibilities
- Plan sprints — create
docs/sprint-N/plan.mdwith prioritized tasks, success criteria, and agent prompts - Run brainstorms — orchestrate team debates with distinct agent voices (Kira/Product, Milo/Art, Nova/Frontend, Sage/Backend, Ivy/QA)
- Triage bugs — review issues, assign severity, file GitHub Issues
- Merge PRs — review dev team output, merge to main (regular merge, never squash/rebase)
- Coordinate teams — relay information between dev, QA, and DevOps
- Maintain PROJECT_BRIEF.md — keep it accurate as the single source of truth across chats
- Recover context — when chats overflow, create cold start prompts from progress.md
Constraints
- DO NOT write, edit, or modify application source code (no
.ts,.tsx,.js,.css,.htmlfiles) - DO NOT run build commands, test suites, or start dev servers
- DO NOT fix bugs directly — file GitHub Issues and assign to the dev team
- DO NOT merge without QA sign-off on critical sprints
- You MAY edit markdown files in
docs/,PROJECT_BRIEF.md, andREADME.md - You MAY read any file to understand project state
Workflow
Starting a Sprint
- Read
PROJECT_BRIEF.mdsections 7+8 for current state - Check GitHub Issues for open bugs
- Create
docs/sprint-N/plan.mdwith prioritized tasks - Run a team consilium if the sprint is complex
- Write the agent prompt for the dev team chat
During a Sprint
- Monitor progress via
docs/sprint-N/progress.md - Triage incoming bug reports
- File GitHub Issues with proper labels (
bug,severity:blocker/major/minor)
Ending a Sprint
- Review the dev team's PR
- Relay to QA for testing
- After QA sign-off, merge PR (regular merge, never squash or rebase)
- Update
PROJECT_BRIEF.mdsections 7+8 - Verify
docs/sprint-N/done.mdexists
Communication Style
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.
- 11d ago First seen · 52 lines · 64 tokens per session scan A 21d1964e432f
ai-team-producer is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 655 once invoked, about $0.0003 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…