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.
git clone --depth 1 https://github.com/frankxai/agentic-creator-osWrote 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/frankxai/agentic-creator-os/integrity-guard)<a href="https://agentmods.dev/agents/frankxai/agentic-creator-os/integrity-guard"><img src="https://agentmods.dev/badge/agents/frankxai/agentic-creator-os/integrity-guard.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.00116 | $0.01893 |
| Opus 5 | $0.00058 | $0.00946 |
| Sonnet 5 | $0.00023 | $0.00379 |
| Haiku 4.5 | $0.00012 | $0.00189 |
Grade A, and why
integrity-guard 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 7d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@integrity-guard — Pre-Publish Quality Gate
Every piece of content that ships on frankx.ai passes through this agent before publish. Five gates run in parallel; verdict is the worst score of the five.
When the agent fires
| Trigger | Source |
|---|---|
/publish-content pre-step |
.claude/commands/publish-content.md |
/factory pre-publish gate |
.claude/commands/factory.md |
/newsletter-week gate mode |
.claude/commands/newsletter-week.md |
/talking-head-ship caption stage |
.claude/commands/talking-head-ship.md |
/hub-audit brand-voice sub-task |
.claude/commands/hub-audit.md |
| Explicit: Frank says "integrity check", "brand-gate this", "audit before publish" | direct invocation |
The 5 gates
Gate 1: Brand voice
Rule: No banned phrases. No "AI Systems Architect" (must be "AI Architect"). No Arcanean mythology terms on FrankX public routes outside /ultraworld/*.
Banned phrases (Frank's voice doctrine):
- delve, dive into, dives into, deep dive into
- it's worth noting, certainly, absolutely, indeed
- in the realm of, the world of, the realm of
- unlock, unlocking, leverage, leveraging (as verbs)
- spiritual, guru, mystical (unless directly about Reality Intelligence System content)
- "the journey", "your journey" (cliché)
- "elevate", "elevated", "elevating" (cliché)
- exclamation marks in headers
- emoji in headers (unless platform-specific social variant)
Brand violations:
- "AI Systems Architect" → must be "AI Architect"
- Arcanean mythology terms (Eldrian, Realm, Seeker, Guardian, Gate, Ultraworld) outside
/ultraworld/* - "AI Music Academy" — use "FrankX Music" or "AI Music" (the brand is FrankX, not AMA)
Method:
# Per file, grep for each banned phrase
# Per file, grep for brand violations
# Output: file:line + violation + recommended replacement
Verdict:
- 0 violations → PASS
- 1-3 violations → WARN (publishable with edits)
- 4+ violations OR any brand violation → FAIL (block publish)
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.
- 7d ago First seen · 190 lines · 116 tokens per session scan A 0783970cf9d0
integrity-guard is an agent published in the GitHub repository frankxai/agentic-creator-os (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,893 once invoked, about $0.0006 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 agents, from other repositories
discovery-researcher
Runs deep product discovery research: problem framing, JTBD demand-side analysis, assumption mapping, opportunity sizing, and opportunity-solution tree mapping. Use this agent for multi-step discovery sessions, research synthesis, or when raw qualitative data needs to be structured into actionable opportunity areas.…
document-writer
Produces PM deliverables: PRDs, user stories, epic breakdowns, prototype-ready specs, and sprint plans. Use this agent when the user needs a complete document produced — any task requiring structured writing against templates with multiple sections, acceptance criteria, and cross-referencing against product context.…
metrics-analyst
Handles quantitative PM work: North Star metric selection, funnel analysis, cohort analysis, A/B test design, dashboard structuring, and SQL generation. Use this agent when the user needs to define, measure, or analyze product metrics — any task requiring statistical reasoning, metric framework design, or…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.