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 apply-gematriagit 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/apply-gematria)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/apply-gematria"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/apply-gematria/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/apply-gematria"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/apply-gematria.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.00089 | $0.02727 |
| Opus 5 | $0.00044 | $0.01363 |
| Sonnet 5 | $0.00018 | $0.00545 |
| Haiku 4.5 | $0.00009 | $0.00273 |
Grade A, and why
apply-gematria 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 6d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Gematria
Compute and analyze gematria — the system of assigning numerical values to Hebrew letters and words. Covers standard (Mispar Hechrachi), ordinal (Mispar Siduri), and reduced (Mispar Katan) methods, isopsephy comparisons between words of equal value, and interpretive frameworks for contemplation.
When to Use
- You want to compute the numerical value of a Hebrew word or phrase
- You are comparing two words to determine if they share a gematria value (isopsephy)
- You need to understand which gematria method is appropriate for a given analysis
- You are studying a biblical verse or divine name and want to uncover numerical correspondences
- You are exploring the relationship between a word's meaning and its numerical value
- You want to connect a numerical result to its position on the Tree of Life
Inputs
- Required: A Hebrew word, phrase, or divine name to analyze (in Hebrew script or transliteration)
- Optional: A second word/phrase for comparison (isopsephy)
- Optional: Preferred gematria method (standard, ordinal, reduced, or all three)
- Optional: Context or question guiding the analysis (e.g., "Why do these two words share a value?")
Procedure
Step 1: Transliterate and Identify the Hebrew Source
Establish the exact Hebrew spelling of the word or phrase.
HEBREW LETTER VALUES — Standard Gematria (Mispar Hechrachi):
Units:
Aleph (A) = 1 Bet (B) = 2 Gimel (G) = 3
Dalet (D) = 4 Heh (H) = 5 Vav (V) = 6
Zayin (Z) = 7 Chet (Ch) = 8 Tet (T) = 9
Tens:
Yod (Y) = 10 Kaf (K) = 20 Lamed (L) = 30
Mem (M) = 40 Nun (N) = 50 Samekh (S) = 60
Ayin (Ay) = 70 Peh (P) = 80 Tzadi (Tz) = 90
Hundreds:
Qoph (Q) = 100 Resh (R) = 200 Shin (Sh) = 300
Tav (Th) = 400
Final Forms (Sofit — used when letter appears at end of word):
Kaf-final = 500 Mem-final = 600 Nun-final = 700
Peh-final = 800 Tzadi-final = 900
Note: Whether final forms carry different values depends on the
gematria system. Standard (Mispar Hechrachi) typically uses the
same values for regular and final forms. The 500-900 values above
follow the extended system (Mispar Gadol).
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.
- 6d ago First seen · 204 lines · 89 tokens per session scan A 3d0675c66893
apply-gematria is a skill published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 2,727 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
analytics
Queries local analytics across OrchestKit projects for agent usage, skill frequency, hook timing, team activity, session replay, cost estimation, and model delegation trends. Privacy-safe with hashed project IDs. Supports time-range filtering and comparative analysis. Use when reviewing performance, estimating costs…
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".
design-feature
Turn a raw idea or existing feature into a designed product SPEC by completing entity, integration, role, and expectation closure. Upserts never destroy recorded decisions. Triggers: "design-feature", "design this feature", "define product scope".
plan-feature
Route designed features or issues into engineering planning and roadmap registration; undesigned work stops at design-feature. Supports --next, --from-issue, and --scaffold. Triggers: "plan-feature", "plan a feature", "plan the next roadmap feature", "create SPEC and TASKS".
product-audit
Audit the whole product across code, quality, process, docs, roadmap, and tooling. Persist one severity-ranked, F-numbered report with proposals; never fix or file work. Triggers: "product-audit", "audit the product", "full health check", "are we product-ready", "CTO review".
audit-docs
Audit cross-document coherence: docs ↔ roadmap ↔ code ↔ fix index ↔ issues. Finds drift — features in docs/ not in the roadmap (or vice versa), fix-index entries already merged/closed, broken documentation-map links, dependency cycles, artifacts in the wrong language, naming-convention violations — and reports them…