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/c0ntr0lledcha0s/claude-code-plugin-automations/initgit clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automationsWrote 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/c0ntr0lledcha0s/claude-code-plugin-automations/init)<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/init"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/init.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 | $0.00019 | $0.02662 |
| Opus 5 | $0.00010 | $0.01331 |
| Sonnet 5 | $0.00004 | $0.00532 |
| Haiku 4.5 | $0.00002 | $0.00266 |
Grade A, and why
init 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 3d 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Workflow Environment
Set up the GitHub workflow environment for the current session. This command gathers project context, syncs issues, and creates environment variables for use by other commands.
Usage
/init # Initialize (skip if already done today)
/init --force # Force re-initialization
Arguments
- --force (optional): Re-initialize even if already done today
What This Does
- Detect Repository: Get owner/repo from git remote
- Get User Info: Current GitHub username
- Find Project Board: Auto-detect most recent active project board
- Get Current Milestone: Find active milestone/sprint
- Analyze Project Scopes: Suggest scope labels based on project structure
- Label Stocktake: Check and report missing standard labels
- Detect Branch: Get current branch and detect related issues and scope
- Sync Issues: Fetch issues (defaults to all issues)
- Set Preferences: Configure defaults (project type, issue filter, default project)
- Create Setup Status: Track which setup steps are complete
- Save Environment: Save context to
.claude/github-workflows/env.json - Show Summary: Display workflow status, label stocktake, and setup recommendations
Environment File
Creates .claude/github-workflows/env.json:
{
"initialized": "2025-01-15T10:30:00Z",
"repository": {
"owner": "owner",
"name": "repo",
"fullName": "owner/repo"
},
"user": {
"login": "username",
"name": "Full Name"
},
"projectBoard": {
"number": 1,
"title": "Sprint 5",
"url": "https://github.com/orgs/owner/projects/1"
},
"milestone": {
"title": "Sprint 5",
"number": 3,
"dueOn": "2025-01-31"
},
"branch": {
"name": "feature/issue-42",
"relatedIssues": [42],
"detectedScope": "auth",
"scopeLabel": "scope:auth"
},
"issueCache": {
"count": 5,
"lastSync": "2025-01-15T10:30:00Z"
},
"labels": {
"existing": 15,
"missing": ["priority:high", "priority:medium"],
"recommended": ["bug", "feature", "enhancement"],
"suggestedScopes": ["claude-component-builder", "self-improvement", "github-workflows"]
},
"setup": {
"labelsComplete": false,
"projectBoardExists": true,
"milestonesExist": true
},
"preferences": {
"projectType": "personal",
"defaultIssueFilter": "all",
"defaultProject": null
}
}
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.
- 3d ago First seen · 341 lines · 19 tokens per session scan A 82b6dbed57c0
init is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 2,662 once invoked, about $0.0001 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 commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间,成员权限,团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.