Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hamzaPixl/pixl-ai/plugin install pixl-crewWrote 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/hamzapixl/pixl-ai/crew-init)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/crew-init"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/crew-init/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/hamzapixl/pixl-ai/crew-init"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/crew-init.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.00061 | $0.01105 |
| Opus 5 | $0.00030 | $0.00553 |
| Sonnet 5 | $0.00012 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade B, and why
crew-init scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. Check if `<target>/.claude/settings.local.json` exists How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Drops lightweight pixl-crew awareness assets into any project so Claude knows about available agents, skills, and conventions without the full plugin source being present.
What gets created
| File | Purpose |
|---|---|
CLAUDE.md |
Project identity + crew agents/skills reference + pixl CLI + operational rules |
.claude/rules/crew-workflow.md |
Explore → Plan → Implement → Commit, frequent commits, parallel execution |
.claude/rules/crew-delegation.md |
Agent routing table, when to use orchestrator, skill-first rules |
.claude/rules/crew-enforcement.md |
Mandatory skill usage and agent delegation enforcement |
.claude/rules/crew-context.md |
When to compact, subagent delegation, token budget, CLAUDE.md sizing |
.claude/settings.local.json |
Scoped permission wildcards (only if file doesn't exist) |
Step 0: Initialize pixl storage + crew
If pixl CLI is available (command -v pixl), run pixl project init in the target directory.
This creates both the .pixl/ directory (SQLite storage) AND installs crew templates
(CLAUDE.md, .claude/rules/, settings.local.json) in a single command.
if command -v pixl &>/dev/null; then
pixl --project <target> project init
# Done — pixl project init handles everything.
# Skip to Step 6 (summary).
fi
Skip silently if pixl is not installed — continue with manual file creation below.
Step 1: Detect project info
- Determine the target directory (argument or cwd)
- Try to detect the project name from (in order):
package.json→namefieldpyproject.toml→namefield- Directory basename
- Ask the user to confirm or override the project name
Step 2: Generate CLAUDE.md
- Read the template from
${CLAUDE_PLUGIN_ROOT}/templates/crew-init/CLAUDE.md.tmpl - Replace
{{PROJECT_NAME}}with the detected/confirmed project name - Write to
<target>/CLAUDE.md- If a
CLAUDE.mdalready exists, ask the user whether to append a crew section or skip
- If a
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 · 98 lines · 61 tokens per session scan B e39dd3a07cc9
crew-init is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,105 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.