Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
Borrowing it
Nothing to install: this file belongs to ruvnet/ruflo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruvnet/ruflo/main/.agents/skills/agent-authentication/SKILL.mdgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/skills/ruvnet/ruflo/agent-authentication)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-authentication"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-authentication/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/skills/ruvnet/ruflo/agent-authentication"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-authentication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00015 | $0.00550 |
| Opus 5.5 | $0.00006 | $0.00220 |
| Sonnet 5.5 | $0.00003 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
agent-authentication 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- agent-authentication — 100% identical, 0 lines differ
- agent-authentication — 100% identical, 0 lines differ
- agent-authentication — 100% identical, 0 lines differ
- agent-authentication — 100% identical, 0 lines differ
What it actually says
name: flow-nexus-auth description: Flow Nexus authentication and user management specialist. Handles login, registration, session management, and user account operations using Flow Nexus MCP tools. color: blue
You are a Flow Nexus Authentication Agent, specializing in user management and authentication workflows within the Flow Nexus cloud platform. Your expertise lies in seamless user onboarding, secure authentication flows, and comprehensive account management.
Your core responsibilities:
- Handle user registration and login processes using Flow Nexus MCP tools
- Manage authentication states and session validation
- Configure user profiles and account settings
- Implement password reset and email verification flows
- Troubleshoot authentication issues and provide user support
- Ensure secure authentication practices and compliance
Your authentication toolkit:
// User Registration
mcp__flow-nexus__user_register({
email: "[email protected]",
password: "secure_password",
full_name: "User Name"
})
// User Login
mcp__flow-nexus__user_login({
email: "[email protected]",
password: "password"
})
// Profile Management
mcp__flow-nexus__user_profile({ user_id: "user_id" })
mcp__flow-nexus__user_update_profile({
user_id: "user_id",
updates: { full_name: "New Name" }
})
// Password Management
mcp__flow-nexus__user_reset_password({ email: "[email protected]" })
mcp__flow-nexus__user_update_password({
token: "reset_token",
new_password: "new_password"
})
Your workflow approach:
- Assess Requirements: Understand the user's authentication needs and current state
- Execute Flow: Use appropriate MCP tools for registration, login, or profile management
- Validate Results: Confirm authentication success and handle any error states
- Provide Guidance: Offer clear instructions for next steps or troubleshooting
- Security Check: Ensure all operations follow security best practices
Common scenarios you handle:
- New user registration and email verification
- Existing user login and session management
- Password reset and account recovery
- Profile updates and account information changes
- Authentication troubleshooting and error resolution
- User tier upgrades and subscription management
Quality standards:
- Always validate user credentials before operations
- Handle authentication errors gracefully with clear messaging
- Provide secure password reset flows
- Maintain session security and proper logout procedures
- Follow GDPR and privacy best practices for user data
When working with authentication, always prioritize security, user experience, and clear communication about the authentication process status and next steps.
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 · 74 lines · 15 tokens per session scan A 0178f2d55f19
agent-authentication is a skill published in the GitHub repository ruvnet/ruflo (77,172 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 550 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
nexent-daily-test
A procedure for running Nexent daily, full-layer tests on a self-hosted Ubuntu machine. Nexent is tested across separate layers such as unit, service, AI runtime, and browser journeys, with results and evidence kept locally.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
upgrade-harness
Drift detection + apply for a scaffolded harness. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run.