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/ruvnet/sublinear-time-solver/login-registrationgit clone --depth 1 https://github.com/ruvnet/sublinear-time-solverWrote 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/ruvnet/sublinear-time-solver/login-registration)<a href="https://agentmods.dev/commands/ruvnet/sublinear-time-solver/login-registration"><img src="https://agentmods.dev/badge/commands/ruvnet/sublinear-time-solver/login-registration.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.00011 | $0.00323 |
| Opus 5 | $0.00005 | $0.00161 |
| Sonnet 5 | $0.00002 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
flow-nexus-auth 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 4d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- flow-nexus-auth — 100% identical, 0 lines differ
- flow-nexus-auth — 100% identical, 0 lines differ
- flow-nexus-auth — 100% identical, 0 lines differ
What it actually says
Flow Nexus Authentication
Quick commands for Flow Nexus login and registration.
Register New Account
mcp__flow-nexus__user_register({
email: "[email protected]",
password: "secure_password",
full_name: "Your Name" // optional
})
Login
mcp__flow-nexus__user_login({
email: "[email protected]",
password: "your_password"
})
Check Auth Status
mcp__flow-nexus__auth_status({ detailed: true })
Logout
mcp__flow-nexus__user_logout()
Password Reset
// Request reset
mcp__flow-nexus__user_reset_password({ email: "[email protected]" })
// Update with token
mcp__flow-nexus__user_update_password({
token: "reset_token",
new_password: "new_secure_password"
})
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" }
})
Quick Start
- Register with your email
- Check your email for verification
- Login to access all features
- Configure auto-refill for uninterrupted service
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.
- 4d ago First seen · 65 lines · 11 tokens per session scan A e1885d8ebb4c
flow-nexus-auth is a command published in the GitHub repository ruvnet/sublinear-time-solver (89 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 323 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-30.
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.