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.
git clone --depth 1 https://github.com/eveld/claudeWrote 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/eveld/claude/share)<a href="https://agentmods.dev/commands/eveld/claude/share"><img src="https://agentmods.dev/badge/commands/eveld/claude/share/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/commands/eveld/claude/share"><img src="https://agentmods.dev/badge/commands/eveld/claude/share.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.00000 | $0.00294 |
| Opus 5.5 | $0.00000 | $0.00118 |
| Sonnet 5.5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
share 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 1mo 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.
What it actually says
Share Documents
You are sharing personal documents to the team's shared namespace.
Initial Response
When this command is invoked, respond with:
I'm ready to share your documents to the team namespace. Please provide the path to your personal document directory (e.g., thoughts/erik/0001-auth-system).
Then wait for the user to provide the path.
Workflow
Step 1: Validate Path
- Check that the provided path exists
- Verify it's in personal namespace format:
thoughts/{username}/NNNN-description/ - Confirm it contains documents to share (research.md, plan.md, etc.)
Step 2: Execute Share
- Use the
share-docsskill to handle the sharing workflow - The skill will:
- Pull latest changes from git
- Find next available shared number
- Copy documents to shared namespace
- Update frontmatter in both copies
- Commit and push immediately
Step 3: Report Result
- Show the shared location
- Confirm what was shared
- Example:
✅ Shared erik/0001-auth-system → shared/0042-auth-system
Important Notes
- Documents are copied, not moved (personal copy remains)
- Shared number is claimed atomically via git push
- If push fails (conflict), the skill retries automatically
- Personal copy is marked with
shared_asfield in frontmatter
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.
- 1mo ago First seen · 44 lines · 0 tokens per session scan A 044388d7edeb
share is a command published in the GitHub repository eveld/claude (10 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 294 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-31.
Other commands, from other repositories
update
You are executing the /import:update command. Re-fetch documentation from original sources.
search
You are executing the /import:search command. Search within all cached documentation.
doc-gen
Generate documentation — JSDoc, docstrings, README sections, or API docs.
gws-drive
Search, upload, download, and share Google Drive files and folders.
gws-sheets
Read, write, and append data to Google Sheets spreadsheets.
gws-docs
Read, create, and append content to Google Docs documents.