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/natea/exomind/user-toolsgit clone --depth 1 https://github.com/natea/ExoMindWhat 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.00014 | $0.00815 |
| Opus 5 | $0.00007 | $0.00407 |
| Sonnet 5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
flow-nexus-user-tools 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 2d 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.
This is a copy
100% identical to flow-nexus-user-tools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Nexus User Tools
Utilities for user management, storage, and system operations.
Profile Management
// Get profile
mcp__flow-nexus__user_profile({
user_id: "your_id"
})
// Update profile
mcp__flow-nexus__user_update_profile({
user_id: "your_id",
updates: {
full_name: "New Name",
bio: "Developer interested in AI",
github_username: "username"
}
})
// Get statistics
mcp__flow-nexus__user_stats({
user_id: "your_id"
})
Storage Management
// Upload file
mcp__flow-nexus__storage_upload({
bucket: "my-bucket",
path: "data/file.json",
content: JSON.stringify(data),
content_type: "application/json"
})
// List files
mcp__flow-nexus__storage_list({
bucket: "my-bucket",
path: "data/",
limit: 100
})
// Get public URL
mcp__flow-nexus__storage_get_url({
bucket: "my-bucket",
path: "data/file.json",
expires_in: 3600 // seconds
})
// Delete file
mcp__flow-nexus__storage_delete({
bucket: "my-bucket",
path: "data/file.json"
})
Real-time Subscriptions
// Subscribe to database changes
mcp__flow-nexus__realtime_subscribe({
table: "tasks",
event: "INSERT", // UPDATE, DELETE, *
filter: "status=eq.pending"
})
// List subscriptions
mcp__flow-nexus__realtime_list()
// Unsubscribe
mcp__flow-nexus__realtime_unsubscribe({
subscription_id: "sub_id"
})
Execution Monitoring
// Monitor execution stream
mcp__flow-nexus__execution_stream_subscribe({
stream_type: "claude-flow-swarm",
deployment_id: "deployment_id"
})
// Get stream status
mcp__flow-nexus__execution_stream_status({
stream_id: "stream_id"
})
// List generated files
mcp__flow-nexus__execution_files_list({
stream_id: "stream_id",
created_by: "claude-flow",
file_type: "javascript"
})
// Get file content
mcp__flow-nexus__execution_file_get({
file_id: "file_id"
})
System Health
// Check system health
mcp__flow-nexus__system_health()
// View audit logs
mcp__flow-nexus__audit_log({
user_id: "your_id",
limit: 100
})
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.
- 2d ago First seen · 152 lines · 14 tokens per session scan A 6fb91d71eee7
flow-nexus-user-tools is a command published in the GitHub repository natea/ExoMind (21 stars, last pushed 10mo ago), licensed MIT. It adds 14 tokens to every session and 815 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to flow-nexus-user-tools, differing in 0 lines, and is treated as a copy.
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.