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.
npx skills add oyi77/1ai-skills --skill crewai-agentsgit clone --depth 1 https://github.com/oyi77/1ai-skillsWrote 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/skills/oyi77/1ai-skills/crewai-agents)<a href="https://agentmods.dev/skills/oyi77/1ai-skills/crewai-agents"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/crewai-agents/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/skills/oyi77/1ai-skills/crewai-agents"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/crewai-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.01560 |
| Opus 5 | $0.00017 | $0.00780 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
crewai-agents 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 8d 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
CrewAI is a framework for orchestrating role-playing AI agents that collaborate to complete complex tasks. Agents have roles, goals, and backstories, and work together in crews with configurable processes (sequential, hierarchical).
Capabilities
- Define agents with roles, goals, and tools
- Create tasks with expected outputs
- Organize crews with sequential or hierarchical processes
- Add custom tools for web search, file I/O, APIs
- Enable memory for context across tasks
- Use delegation for agent-to-agent communication
When to Use
Trigger phrases:
-
"crewai agents"
-
"CrewAI multi-agent orchestration — agents, tasks, crews, tools, memory, delegati"
-
Building multi-agent systems for research, writing, or analysis
-
Needing role-specialized agents collaborating on tasks
-
Wanting structured task delegation with accountability
-
Building autonomous workflows with human-in-the-loop options
When NOT to Use
- Task is outside your authorization scope
- You need to implement controls (use implementing-* skills)
- Task is about analysis, not action (use analyzing-* skills)
- You don't have access to target systems
- Task requires compliance expertise (consult professionals)
- Task is about defense, not offense (use defensive skills)
Pseudo Code
# Example workflow for this skill
def execute(input_data):
# Step 1: Validate input
if not input_data:
raise ValueError("Input data is required")
# Step 2: Process core logic
result = process(input_data)
# Step 3: Validate output
validate_output(result)
return result
Agent and Crew Definition
from crewai import Agent, Task, Crew, Process
from crewai_tools import SerperDevTool, FileReadTool
# Tools
search_tool = SerperDevTool()
file_tool = FileReadTool()
# Agents
researcher = Agent(
role="Senior Research Analyst",
goal="Find comprehensive information on the given topic",
backstory="You are an experienced researcher with expertise in finding and synthesizing information from multiple sources.",
tools=[search_tool],
verbose=True,
allow_delegation=False,
)
writer = Agent(
role="Content Writer",
goal="Write engaging, well-structured content based on research",
backstory="You are a skilled writer who transforms research into compelling narratives.",
tools=[file_tool],
verbose=True,
allow_delegation=False,
)
reviewer = Agent(
role="Quality Reviewer",
goal="Ensure content is accurate, well-structured, and meets standards",
backstory="You are a meticulous editor with years of experience in content quality assurance.",
verbose=True,
allow_delegation=True, # Can delegate back to writer
)
# Tasks
research_task = Task(
description="Research the latest trends in AI agents for 2026",
expected_output="A comprehensive report with key findings, trends, and data points",
agent=researcher,
)
writing_task = Task(
description="Write a blog post based on the research findings",
expected_output="A 1500-word blog post with introduction, key sections, and conclusion",
agent=writer,
context=[research_task], # Depends on research
)
review_task = Task(
description="Review the blog post for accuracy and quality",
expected_output="A quality assessment with specific improvement suggestions",
agent=reviewer,
context=[writing_task],
)
# Crew
crew = Crew(
agents=[researcher, writer, reviewer],
tasks=[research_task, writing_task, review_task],
process=Process.sequential, # Execute tasks in order
verbose=True,
memory=True, # Enable shared memory
)
# Execute
result = crew.kickoff()
print(result)
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.
- 8d ago First seen · 237 lines · 34 tokens per session scan A 5cfbfd3f9d53
crewai-agents is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,560 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
crewai-multi-agent
Multi-agent orchestration framework for autonomous AI collaboration. Use when building teams of specialized agents working together on complex tasks, when you need role-based agent collaboration with memory, or for production workflows requiring sequential/hierarchical execution. Built without LangChain dependencies…
letter-hooker
Erweitert automation-self-care um Letter Hooks, Preflight-Bootloader, Dokument-Traversierungsregeln und selbstheilende Prompt-Kontext- Anreicherung für KI-Agenten und CLIs ohne native, ereignisgetriebene JSON-Lifecycle-Hooks (wie Antigravity / Gemini CLI). Nutzen, wenn ein Agent Preflight-Regeln injizieren, vor…
agentic-os
Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases.
cost-efficiency-analyzer
Analyzes cost structure, cost efficiency, and expense management from P&L data. Use when the user asks about costs, expenses, COGS, operating expenses, cost ratios, cost control, spending efficiency, margin compression from cost side, or wants to understand where money is going. Also use for "are we spending too…
lat-md-knowledge-graph
Design or audit a repo-local markdown knowledge graph with wiki links, source-code backlinks, drift checks, and searchable sections. Use when AGENTS.md/CLAUDE.md is too flat for a large codebase or when a custom harness needs durable structured project memory.