Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AlexFischman/mcp-skill-creator-agencynpx agentmods add rules/alexfischman/mcp-skill-creator-agency/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/rules/alexfischman/mcp-skill-creator-agency/workflow)<a href="https://agentmods.dev/rules/alexfischman/mcp-skill-creator-agency/workflow"><img src="https://agentmods.dev/badge/rules/alexfischman/mcp-skill-creator-agency/workflow.svg" alt="Measured on agentmods" 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.04018 | $0.04018 |
| Opus 5 | $0.02009 | $0.02009 |
| Sonnet 5 | $0.00804 | $0.00804 |
| Haiku 4.5 | $0.00402 | $0.00402 |
Grade A, and why
workflow 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 7d 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.
This is a copy
88% identical to agency-swarm-workflow — 88 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agency Swarm is the framework built on the OpenAI Agents SDK. It allows anyone to create a collaborative swarm of agents (Agencies), each with distinct roles and capabilities. Your primary role is to architect tools and agents that fulfill specific needs within the agency.
The following steps outline how to build AI agents with Agency Swarm:
- Setup: Create a to-do list for yourself and activate a virtual environment. If virtual environment does not exist, create it.
- Project Exploration: Understand the existing project structure, check for PRD, and remove example agents if present.
- Folder Structure and Template Creation: Create the Agent Templates for each agent using the CLI Commands provided below.
- Tool Development: Develop each tool and place it in the correct agent's tools folder, ensuring it is robust and ready for production environments.
- Agent Creation: Create agent classes and instructions for each agent, ensuring correct folder structure.
- Agency Creation: Create the agency class in the agency folder, properly defining the communication flows between the agents.
- Testing: Test each tool for the agency, and the agency itself, to ensure they are working as expected.
- Iteration: Repeat the above steps as instructed by the user, until the agency performs consistently to the user's satisfaction.
You will find a detailed guide for each of the steps below. Read this entire file first before proceeding.
Step 1: Project Exploration
Before starting any work, you must understand the current state of the project and prepare it for agent creation.
Exploration Checklist
- Check root directory structure: List files and folders in the project root
- Look for PRD: Check if
prd.txtexists in the root directory - Check for example agents: Look for folders like
example_agent/orexample_agent2/ - Review existing files: Read
agency.py,shared_instructions.md,agent_name/instructions.md,agent_name/tools/, etc.
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.
- 7d ago First seen · 410 lines · 4,018 tokens per session scan A a62c09857f33
workflow is a cursor rule published in the GitHub repository AlexFischman/mcp-skill-creator-agency (2 stars, last pushed 9mo ago), licensed MIT. It adds 4,018 tokens to every session, about $0.0201 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to agency-swarm-workflow, differing in 88 lines, and is treated as a copy.
Other cursor rules, from other repositories
global-context
Global repository rules and architecture patterns.
load-skills
Reference and apply custom developer skills for project workflows.
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
testing-and-security
Testing and Security Guidelines for FastAPI Applications Including Unit Testing, Environment Variable Management, and Authentication Security.
cursorrules
คุณคือผู้ช่วยเขียนโค้ดผู้เชี่ยวชาญสำหรับโปรเจกต์ "Chonost Ecosystem" ภารกิจหลักคือช่วยสร้างเครื่องมือสร้างสรรค์ที่มี UX ไร้รอยต่อ.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.