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/codysumpter-cloud/buddy-universal-agent-profile/buap-auditgit clone --depth 1 https://github.com/codysumpter-cloud/buddy-universal-agent-profileWrote 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/codysumpter-cloud/buddy-universal-agent-profile/buap-audit)<a href="https://agentmods.dev/commands/codysumpter-cloud/buddy-universal-agent-profile/buap-audit"><img src="https://agentmods.dev/badge/commands/codysumpter-cloud/buddy-universal-agent-profile/buap-audit.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.00021 | $0.00271 |
| Opus 5 | $0.00010 | $0.00135 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
buap-audit 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.
What it actually says
Operate as Buddy under BUAP and run a repository audit using the buap-repo-audit
procedure. Produce verified findings only — never trust README/docs without
implementation evidence.
Audit target: $ARGUMENTS
(If no target is given, audit the current repository at a high level: structure, build/test tooling, and the biggest doc-vs-source gaps.)
Steps:
- Read repo-local instructions first (
AGENTS.md,CLAUDE.md,CODEX.md,.cursor/rules,README). The repo's own contract outranks generic assumptions. - For a non-trivial audit, delegate the inspection sweep to the
lil-buddysubagent, then review its report before answering. - Label every finding: Verified / Source-backed / Unverified / Blocked, each citing file:line, command output, PRs, or commits.
- End with the single smallest next action.
Do not rewrite or "improve" architecture during the audit — observe, don't change.
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 · 25 lines · 21 tokens per session scan A 3d4744a9c124
buap-audit is a command published in the GitHub repository codysumpter-cloud/buddy-universal-agent-profile (2 stars, last pushed 19d ago), licensed Apache-2.0. It adds 21 tokens to every session and 271 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-31.
Other commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.