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 skills add pjt222/agent-almanac --skill brahma-bhagagit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/brahma-bhaga)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/brahma-bhaga"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/brahma-bhaga/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/pjt222/agent-almanac/brahma-bhaga"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/brahma-bhaga.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00104 | $0.01983 |
| Opus 5.5 | $0.00042 | $0.00793 |
| Sonnet 5.5 | $0.00021 | $0.00397 |
| Haiku 4.5 | $0.00010 | $0.00198 |
Grade A, and why
brahma-bhaga 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brahma Bhaga
Generative creation from void or ambiguity — structured emergence of new patterns, approaches, and solutions where none existed before.
When to Use
- After
shiva-bhagadissolution has cleared stale patterns and created space - Facing a genuinely novel problem with no obvious template or precedent
- The user's request requires invention rather than retrieval or adaptation
- Multiple possible approaches exist and none has been chosen — the creative act is the choice itself
- A blank slate: new file, new project, new architecture, new approach
- When incremental modification has reached its limits and a fresh design is needed
Inputs
- Required: The creative goal or void to fill (available from conversation context)
- Optional: Constraints that bound the creation (user requirements, technical limitations)
- Optional: Seeds — fragments, inspirations, or partial ideas that inform the creation
- Optional: What was dissolved (
shiva-bhagaoutput) — understanding what failed guides what to create
Procedure
Step 1: Survey the Void
Before creating, understand the space available for creation.
Creative Space Assessment:
+---------------------+---------------------------+------------------------+
| Dimension | Questions | Determines |
+---------------------+---------------------------+------------------------+
| Constraints | What MUST the creation | The boundary within |
| | satisfy? What is non- | which creativity |
| | negotiable? | operates |
+---------------------+---------------------------+------------------------+
| Freedom | What is NOT specified? | The degrees of freedom |
| | Where does the user leave | available for creative |
| | room for creative choice? | choice |
+---------------------+---------------------------+------------------------+
| Seeds | What fragments, partial | The starting material |
| | ideas, or inspirations | that informs but does |
| | already exist? | not dictate |
+---------------------+---------------------------+------------------------+
| Anti-patterns | What was tried before and | The space to avoid — |
| | failed? What approaches | creation that repeats |
| | were dissolved? | dissolved patterns |
+---------------------+---------------------------+------------------------+
| Context | What exists around the | The environment the |
| | void? What must the | creation must fit |
| | creation integrate with? | into |
+---------------------+---------------------------+------------------------+
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 · 178 lines · 104 tokens per session scan A 9f5c161384fb
brahma-bhaga is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 104 tokens to every session and 1,983 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…
fold-findings
Repair persisted fix-now findings in compatible atomic batches: root-cause fixes, green gate, commit/push, and per-row folded: yes updates. Never reclassify or substitute backlog notes. Triggers: "fold-findings", "fix the review findings", "repair audit blockers".
init-workspace
Adapt the workflow scaffold to a new repository or add only missing substrate blocks to an existing install. Every install, hook, and overwrite needs explicit consent. Triggers: "init-workspace", "set up agentic workflow", "upgrade workflow scaffold".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling; it owns the repo-wide bug hunt, security research, and broken-version investigation (scoped and budgeted per dimension, as distinct from review-change's change-scoped review). Persist one severity-ranked, F-numbered report with…
review-change
Review a change with only applicable internal axes, classify every finding, persist fix-now work, and return one evidence-backed decision. Findings only; --adversarial N uses isolated reviewers; --synthesize fuses supplied reviewer tables. Triggers: "review-change", "review this change", "adversarial review".