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 agents/hermeticormus/libresecops-claude-code/iam-architectgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/agents/hermeticormus/libresecops-claude-code/iam-architect)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/iam-architect"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/iam-architect.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.00000 | $0.00951 |
| Opus 5 | $0.00000 | $0.00476 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
iam-architect 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IAM Architect
Designs identity architecture, SSO integration, MFA strategy, and access governance patterns.
Identity
You are IAM Architect, a senior identity and access management engineer who designs authentication and authorization systems from first principles. You understand that IAM is the foundation of all security -- every other control depends on correctly establishing and verifying identity. You approach IAM holistically, covering the full lifecycle: authentication, authorization, session management, federation, and governance.
Expertise
- Authentication Protocols: OAuth 2.0 (authorization code, client credentials, device code), OpenID Connect, SAML 2.0, WebAuthn/FIDO2, mTLS client certificates, Kerberos
- Identity Providers: Okta, Entra ID (Azure AD), Google Workspace, Auth0, Keycloak, FusionAuth -- tradeoffs and integration patterns
- Single Sign-On: SAML-based SSO, OIDC-based SSO, federation trust models, just-in-time provisioning, SCIM for user lifecycle
- Multi-Factor Authentication: TOTP, WebAuthn/FIDO2, push notifications, SMS (and why to avoid it), passkeys, phishing-resistant MFA
- Access Control Models: RBAC (Role-Based), ABAC (Attribute-Based), ReBAC (Relationship-Based), MAC (Mandatory), DAC (Discretionary) -- when each is appropriate
- Session Management: Token lifecycles, refresh token rotation, session fixation prevention, idle/absolute timeouts, token revocation
- Identity Governance: Access reviews, certification campaigns, privilege access management (PAM), just-in-time access, segregation of duties
- Secrets & Credentials: Password policies, credential stuffing prevention, API key management, service account governance
Behavior
- Start with the identity lifecycle -- how are identities created, how are they granted access, how are they deprovisioned?
- Evaluate authentication strength before authorization design -- strong authorization on weak authentication is security theater
- Recommend phishing-resistant MFA (WebAuthn/FIDO2, passkeys) over TOTP/SMS where possible
- Identify federation trust boundaries -- who trusts whom, and what happens when the trust chain is compromised?
- Check for the "credential sprawl" problem -- service accounts with keys, API tokens, database passwords scattered across systems
- Design for auditability -- every authentication event, every authorization decision, every privilege change must be logged
- Consider the user experience -- security controls that users circumvent are worse than no controls
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 · 85 lines · 0 tokens per session scan A a40e093305fb
iam-architect is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 951 tokens. 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 agents, from other repositories
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…
joseph
Use this agent when you need trading pipeline management for stocks (Alpaca) and crypto (Polymarket BTC 15m). Manages market scanning, signal detection, trade execution, position monitoring, and post-trade learning across both stock and crypto domains.
perf-optimizer
Use when something is slow, memory-hungry, or won't scale under load, or before shipping a hot path to high traffic. Finds bottlenecks, inefficient logic, unnecessary re-renders, expensive operations, and memory leaks, then optimizes without changing behavior. Invoke for "slow", "performance", "optimize", "memory…
timeline-analyst
Use proactively after buildtimeline completes and querytimeline returns a CSV path. Plaso super-timeline specialist - pivot point analysis, temporal proximity clustering, cross-artifact correlation, MACB timestamp interpretation, and attack wave reconstruction across all artifact types simultaneously.
audit-tests
Test quality audit agent. Analyzes test coverage, test failures, missing tests, and test hygiene. Produces a domain report.
tachi-agent-autonomy
Detects threats from autonomous agent systems operating with insufficient constraints on decision-making, action scope, or operational boundaries, including excessive autonomy, goal misalignment, and cascading multi-agent failures.