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/cyperx84/claude-code-plugin-examples/managegit clone --depth 1 https://github.com/cyperx84/claude-code-plugin-examplesWhat 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.00009 | $0.00899 |
| Opus 5 | $0.00005 | $0.00449 |
| Sonnet 5 | $0.00002 | $0.00180 |
| Haiku 4.5 | $0.00001 | $0.00090 |
Grade A, and why
manage 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 yesterday.
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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Cloud Storage
Manage: $ARGUMENTS (operation and parameters)
Using AWS S3 MCP for storage management
Management Operations
1. List Operations
# List buckets
aws s3 ls
# List files in bucket
aws s3 ls s3://my-bucket/
# Recursive list
aws s3 ls s3://my-bucket/ --recursive
# With file sizes
aws s3 ls s3://my-bucket/ --human-readable --summarize
2. File Operations
# Copy within S3
aws s3 cp s3://bucket1/file.txt s3://bucket2/file.txt
# Move file
aws s3 mv s3://bucket/old-path/file.txt s3://bucket/new-path/file.txt
# Delete file
aws s3 rm s3://bucket/file.txt
# Delete directory
aws s3 rm s3://bucket/directory/ --recursive
3. Permissions Management
# Make public
aws s3api put-object-acl --bucket my-bucket --key file.txt --acl public-read
# Make private
aws s3api put-object-acl --bucket my-bucket --key file.txt --acl private
# Bucket policy
aws s3api put-bucket-policy --bucket my-bucket --policy file://policy.json
# CORS configuration
aws s3api put-bucket-cors --bucket my-bucket --cors-configuration file://cors.json
4. Lifecycle Management
// Auto-delete old files
const lifecycleConfig = {
Rules: [
{
Id: 'Delete old logs',
Status: 'Enabled',
Prefix: 'logs/',
Expiration: { Days: 30 }
},
{
Id: 'Archive old backups',
Status: 'Enabled',
Prefix: 'backups/',
Transitions: [
{ Days: 30, StorageClass: 'GLACIER' }
]
}
]
};
await s3.putBucketLifecycleConfiguration({
Bucket: 'my-bucket',
LifecycleConfiguration: lifecycleConfig
});
5. Versioning
# Enable versioning
aws s3api put-bucket-versioning \
--bucket my-bucket \
--versioning-configuration Status=Enabled
# List versions
aws s3api list-object-versions --bucket my-bucket --prefix file.txt
# Restore previous version
aws s3api copy-object \
--bucket my-bucket \
--copy-source my-bucket/file.txt?versionId=VERSION_ID \
--key file.txt
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.
- yesterday First seen · 161 lines · 9 tokens per session scan A ed624ddeec0b
manage is a command published in the GitHub repository cyperx84/claude-code-plugin-examples (2 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 899 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.