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/signalcompose/claude-tools/export-communitygit clone --depth 1 https://github.com/signalcompose/claude-toolsWrote 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/signalcompose/claude-tools/export-community)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/export-community"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/export-community.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.00007 | $0.01182 |
| Opus 5 | $0.00003 | $0.00591 |
| Sonnet 5 | $0.00001 | $0.00236 |
| Haiku 4.5 | $0.00001 | $0.00118 |
Grade A, and why
export-community 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ypm:export-community - Export Private Repository to Public Community Version
This command exports from a private repository to public community version.
First run performs interactive setup, subsequent runs execute export automatically.
Your Role
Execute the following steps strictly:
STEP 0: Language Detection
Check ~/.ypm/config.yml for settings.language setting.
Detection rules:
- If
settings.languageis set, use that language - If not set or config doesn't exist, detect from user's recent messages:
- User's recent message contains Japanese keywords -> Japanese
- Otherwise (English only) -> English
- Default: English
Note detected language internally for use in STEP 3 and STEP 4-2 AskUserQuestion.
STEP 1: Check Current Directory and Branch
pwd
git branch --show-current
Check current directory and report to user.
STEP 2: Check Configuration File Existence
ls -la .export-config.yml 2>/dev/null || echo "NOT_FOUND"
Decision:
.export-config.ymlexists -> Skip to STEP 4.export-config.ymldoesn't exist -> Proceed to STEP 3
STEP 3: Interactive Setup (First Run Only)
Use AskUserQuestion tool to collect the following information:
Question 1: Repository Configuration
Collect:
- Private repo path (current directory or custom path)
- Public repo URL (owner/name for new, URL for existing)
Question 2: Files to Exclude
Recommended exclusions:
- CLAUDE.md - Personal Claude Code configuration
- config.yml - Personal configuration with local paths
- PROJECT_STATUS.md - Personal project management data
- docs/research/ - Internal research documents
Question 3: Commit Message Sanitization
Collect sensitive keywords to remove from commit messages (comma-separated).
STEP 3-2: Create .export-config.yml
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 · 200 lines · 7 tokens per session scan A 4b1abeec4c7a
export-community is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 7d ago), licensed MIT. It adds 7 tokens to every session and 1,182 once invoked, about $0.0000 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.