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 agentmods add commands/jaan-mustafa/10x-team/init-projectgit clone --depth 1 https://github.com/Jaan-Mustafa/10x-TeamWrote 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/commands/jaan-mustafa/10x-team/init-project)<a href="https://agentmods.dev/commands/jaan-mustafa/10x-team/init-project"><img src="https://agentmods.dev/badge/commands/jaan-mustafa/10x-team/init-project.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.00000 | $0.00762 |
| Opus 5 | $0.00000 | $0.00381 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
init-project 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/init-project — Initialize Project State for 10x-Team
Set up the shared project state files that enable communication between all 10x-Team skills.
Steps
-
Check if state already exists — Look for a
.10x/directory in the project root. If it exists, tell the user and ask if they want to reset it. -
Create the
.10x/directory, theadrs/subfolder, and three state files:
.10x/adrs/ directory
Create this folder for Architecture Decision Records. Add a .gitkeep file so it's tracked by git. ADRs will be written here during the Design phase before any implementation begins.
.10x/decisions.md
# Project Decisions
> This file is the shared brain of the 10x-Team. Every role reads it before acting and writes to it after deciding. Append only — never delete or overwrite another role's decisions.
## Project: [Ask user for project name]
Started: [Today's date]
---
<!-- Decisions are appended below by each role. Format:
### [Date] — [Role]: [Decision Title]
- **Decision:** What was decided
- **Why:** Business/technical justification
- **Alternatives considered:** What else was evaluated
- **Trade-offs accepted:** What we're giving up
- **Impacts:** Which roles/components this affects
-->
.10x/status.md
# Project Status
## Project: [Same project name]
**Current Phase:** Brainstorming
**Last Updated:** [Today's date] by init-project
**Health:** On Track
## Progress
### Done
(none yet)
### In Progress
(none yet)
### Pending
- [ ] CTO: Strategic direction and tech decisions
- [ ] PM: Requirements and scope definition
- [ ] Architect: System design
- [ ] Staff Engineer: Coding standards and patterns
- [ ] EM: Task breakdown and estimation
- [ ] Senior Engineer: Implementation planning
- [ ] SDE: Code implementation
- [ ] DBA: Schema and data modeling
- [ ] Security: Threat model and security review
- [ ] QA: Test strategy and verification
- [ ] DevOps: CI/CD and deployment
- [ ] SRE: Monitoring and reliability
### Blocked
(none)
## Risks
(none identified yet)
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.
- 5d ago First seen · 106 lines · 0 tokens per session scan A 3619dbeec3ff
init-project is a command published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 762 tokens. 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-30.
Other commands, from other repositories
cancel-ralph
Cancel active Ralph Loop.
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
luyao-write
Command "luyao-write" from wordflowlab/novel-writer, covering 路遥风格现实主义创作, 使用方法, 内容类型, 示例用法 and 农村生活场景.