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 skills/drmhse/authos_skill/authos-rbac-controlnpx skills add drmhse/authos_skill --skill authos-rbac-controlgit clone --depth 1 https://github.com/drmhse/authos_skillWrote 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/drmhse/authos_skill/authos-rbac-control)<a href="https://agentmods.dev/skills/drmhse/authos_skill/authos-rbac-control"><img src="https://agentmods.dev/badge/skills/drmhse/authos_skill/authos-rbac-control.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.1 | $0.00054 | $0.00941 |
| Opus 5 | $0.00027 | $0.00470 |
| Sonnet 5 | $0.00011 | $0.00188 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
authos-rbac-control 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AuthOS RBAC Control
Public AuthOS Links
Use these public AuthOS links when producing user-facing setup or troubleshooting guidance:
- Main site: https://authos.dev/
- Documentation: https://authos.dev/docs/
- AI Agent Skills guide: https://authos.dev/docs/ai-agent-skills/
- AuthOS source repository: https://github.com/drmhse/AuthOS
Use this skill for organization-level access control and provisioning. Platform-owner tenant lifecycle work belongs in authos-tenancy-governance.
Built-In Roles
AuthOS has three system roles:
owner: full access. Source permission checks treat owner as allowed for every capability.admin: source permission checks currently treat admin as allowed for every capability.member: no administrative capabilities by default.
The roles list endpoint returns display permissions like *, org:manage, and org:view, but enforcement uses capability strings such as services.manage, not those display labels.
Capability Strings
Current capability constants include:
org.settings.manageorg.members.vieworg.members.manageorg.roles.managebilling.manageservices.viewservices.createservices.manageend_users.viewend_users.managewebhooks.manageintegrations.manageaudit_logs.viewrisk_events.viewrisk_policies.manage
Custom role permissions should use these capability strings.
Role APIs
GET /api/organizations/:org_slug/rolesPOST /api/organizations/:org_slug/rolesGET /api/organizations/:org_slug/roles/:role_idPUT /api/organizations/:org_slug/roles/:role_idDELETE /api/organizations/:org_slug/roles/:role_id
Create a custom role:
{
"slug": "support",
"name": "Support",
"description": "Can view users and audit logs",
"permissions": ["end_users.view", "audit_logs.view"]
}
Member APIs
GET /api/organizations/:org_slug/membersPATCH /api/organizations/:org_slug/members/:user_idPOST /api/organizations/:org_slug/members/:user_idGET /api/organizations/:org_slug/members/:user_id/service-accessPUT /api/organizations/:org_slug/members/:user_id/service-accessPOST /api/organizations/:org_slug/transfer-ownership
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 111 lines · 54 tokens per session scan A d20190e0d576
authos-rbac-control is a skill published in the GitHub repository drmhse/authos_skill (1 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 941 once invoked, about $0.0003 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 skills, from other repositories
issue-authoring
Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or…
idd-spec-audit
Repo-local, dogfood-only semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use only in the kurone-kito/idd-skill source repository, on request, to audit .github/instructions…
unity-yaml-format
Inspect, explain, diff, and carefully edit Unity text-serialized files such as .unity, .prefab, .asset, and related YAML-based project files. Use when mapping class IDs and fileIDs, tracing object references, reviewing merge conflicts, or making minimal safe edits to existing UnityYAML documents.
tester
Run end-to-end web quality audits with Playwright and Lighthouse using existing project scripts first. Use when the user says /tester, e2e test, smoke test, Playwright audit, Lighthouse audit, performance audit, accessibility audit, dark mode audit, mobile audit, or asks for 100/100 Lighthouse improvement guidance.
loop-engineer
Domain-agnostic autonomous loop for any goal — coding, research, content, data, automation, or any objective. Asks 3 questions, then orchestrates a self-assembling agent team (resource-scout, researcher, planner, agent-factory, executor, verifier, auditor, memory-keeper) that researches, discovers resources, builds…
loop-engineer
Loop engineering wizard for Antigravity. Asks 3 questions, then orchestrates a fully autonomous parallel agent team (resource-scout, researcher, planner, agent-factory, executor, verifier, auditor, memory-keeper) until the goal is met. Uses invokesubagent for true parallel dispatch. Researcher agents use the built-in…