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 Bilal140202/the-lord-of-the-skills --skill brycewang-stanford__awesome-journal-skillsgit clone --depth 1 https://github.com/Bilal140202/the-lord-of-the-skillsWrote 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/bilal140202/the-lord-of-the-skills/brycewang-stanford__awesome-journal-skills)<a href="https://agentmods.dev/skills/bilal140202/the-lord-of-the-skills/brycewang-stanford__awesome-journal-skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/brycewang-stanford__awesome-journal-skills/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/bilal140202/the-lord-of-the-skills/brycewang-stanford__awesome-journal-skills"><img src="https://agentmods.dev/badge/skills/bilal140202/the-lord-of-the-skills/brycewang-stanford__awesome-journal-skills.svg" alt="Reviewed on agentmods" width="80" 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.00078 | $0.01361 |
| Opus 5 | $0.00039 | $0.00681 |
| Sonnet 5 | $0.00016 | $0.00272 |
| Haiku 4.5 | $0.00008 | $0.00136 |
Grade A, and why
jpe-submission 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 12d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submission Preflight (jpe-submission)
When to trigger
- "Submitting tomorrow" — the last mechanical check before pressing submit
- Unsure what the Editorial Express portal requires as separate files
- Confirming format, references, and fee handling are correct
JPE (founded 1892, edited at the University of Chicago; lead editor Esteban Rossi-Hansberg) is published by the University of Chicago Press and processed through the Editorial Express system (author portal: editorialmanager.com/jpolec). Review is single-blind (referees see authors; authors do not see referees), so author-anonymization is not required — this differs from a double-blind journal. A submission fee applies: $250 for nonsubscribers, $125 for individual JPE subscribers, non-refundable even if the paper is desk-rejected; a waiver is available to authors who completed three or more JPE referee reports in the prior 12 months. Since the 2023 launch of the companion journals JPE Microeconomics (lead editor John List) and JPE Macroeconomics (lead editor Greg Kaplan), decide up front whether your paper targets the flagship JPE or a field companion. Verify the current fee and guidelines on the official page before submitting; everything below is the durable structure of a JPE submission.
Pre-submission checklist
Format
- Manuscript is a single PDF, double-spaced, with figures/tables either embedded or at the end per current guidelines
- Sections ordered logically (intro → model/theory → data → strategy → results → mechanisms/robustness → conclusion)
- Equations numbered and referenced as "equation (n)"
- Figures legible in grayscale; tables self-contained with full notes
- Online appendix prepared as a separate file (proofs, full robustness, descriptive tables)
References (house style)
- Chicago author-date citations throughout (e.g., "Becker 1968") — not numbered/bracket
- Reference list complete and consistently formatted in University of Chicago Press author-date style
- Every in-text citation appears in the list; every list entry is cited
- Canonical theory the paper engages is cited (a frequent referee snag)
What ships with it
58 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- canonical__SKILL.md 6.0 KB
- SKILL_1.md 5.8 KB
- SKILL_10.md 4.0 KB
- SKILL_11.md 3.8 KB
- SKILL_12.md 3.5 KB
- SKILL_13.md 5.7 KB
- SKILL_14.md 4.8 KB
- SKILL_15.md 5.7 KB
- SKILL_16.md 5.2 KB
- SKILL_17.md 5.6 KB
- SKILL_18.md 5.6 KB
- SKILL_19.md 6.0 KB
- SKILL_2.md 5.6 KB
- SKILL_20.md 5.6 KB
- SKILL_21.md 4.7 KB
- SKILL_22.md 6.4 KB
- SKILL_23.md 4.2 KB
- SKILL_24.md 5.7 KB
- SKILL_25.md 6.3 KB
- SKILL_26.md 5.6 KB
- SKILL_27.md 5.9 KB
- SKILL_28.md 6.0 KB
- SKILL_29.md 5.5 KB
- SKILL_3.md 6.0 KB
- SKILL_30.md 6.1 KB
- SKILL_31.md 4.3 KB
- SKILL_32.md 4.9 KB
- SKILL_33.md 3.8 KB
- SKILL_34.md 5.8 KB
- SKILL_35.md 6.0 KB
- SKILL_36.md 4.9 KB
- SKILL_37.md 5.2 KB
- SKILL_38.md 6.3 KB
- SKILL_39.md 6.0 KB
- SKILL_4.md 4.7 KB
- SKILL_40.md 5.6 KB
- SKILL_41.md 4.2 KB
- SKILL_42.md 4.5 KB
- SKILL_43.md 5.5 KB
- SKILL_44.md 5.2 KB
- SKILL_45.md 5.8 KB
- SKILL_46.md 4.7 KB
- SKILL_47.md 5.5 KB
- SKILL_48.md 5.0 KB
- SKILL_49.md 8.9 KB
- SKILL_5.md 4.3 KB
- SKILL_50.md 8.9 KB
- SKILL_51.md 6.4 KB
- SKILL_52.md 6.0 KB
- SKILL_53.md 6.2 KB
- SKILL_54.md 4.6 KB
- SKILL_55.md 4.8 KB
- SKILL_56.md 5.0 KB
- SKILL_57.md 4.3 KB
- SKILL_6.md 5.4 KB
- SKILL_7.md 3.7 KB
- SKILL_8.md 5.9 KB
- SKILL_9.md 4.3 KB
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.
- 12d ago First seen · 86 lines · 78 tokens per session scan A 853a203d8996
jpe-submission is a skill published in the GitHub repository Bilal140202/the-lord-of-the-skills (4 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 1,361 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-08-31.
Other skills, from other repositories
serpsmith
Publish SEO articles reliably across AI-agent runtimes.
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
performing-threat-hunting-with-yara-rules
Use YARA pattern-matching rules to hunt for malware, suspicious files, and indicators of compromise across filesystems and memory dumps. Covers rule authoring, yara-python scanning, and integration with threat intel feeds.
hunt-idor
Hunting skill for idor vulnerabilities. Built from 26 public bug bounty reports. Use when hunting idor on any target.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
testrail
Sync tests with TestRail. Use when user mentions "testrail", "test management", "test cases", "test run", "sync test cases", "push results to testrail", or "import from testrail".