Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Jessinra/Lorekeepernpx agentmods add skills/jessinra/lorekeeper/proposal-filingWrote 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/jessinra/lorekeeper/proposal-filing)<a href="https://agentmods.dev/skills/jessinra/lorekeeper/proposal-filing"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/proposal-filing/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/jessinra/lorekeeper/proposal-filing"><img src="https://agentmods.dev/badge/skills/jessinra/lorekeeper/proposal-filing.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.00041 | $0.01159 |
| Opus 5.5 | $0.00016 | $0.00464 |
| Sonnet 5.5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
proposal-filing 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proposal Filing
Create a new Lorekeeper proposal ticket end-to-end.
Prerequisites
- Working directory:
~/Code/lorekeeper/ - Git identity:
git config user.nameanduser.emailmust be set
Steps
1. Get the next ticket number
Always use the GitHub Issues-based script — this works from any git state (no need to pull latest):
cd ~/Code/lorekeeper
./scripts/next-ticket-number.sh -m
This queries GitHub Issues for the highest existing LKPR-N and returns the next one, e.g. LKPR-43. Also available as machine-parseable:
./scripts/next-ticket-number.sh # just "LKPR-43"
Do NOT rely on the local git state — you may not have the latest main branch, leading to duplicate ticket numbers.
2. Create the markdown file
cp backlogs/TEMPLATE.md backlogs/LKPR-N-<short-slug>.md
Fill in frontmatter:
---
id: LKPR-N
title: Short descriptive title
type: feature # feature | bug | enhancement | research | chore
status: S:proposal
priority: P2:medium # P0:critical | P1:high | P2:medium | P3:low
sprint: ~
rice_score: ~
filed_by: Diana # whoever is filing
filed_date: YYYY-MM-DD
github_issue: ~ # fill after step 3
---
Required body sections: Problem, Solution, Acceptance Criteria, Affected Files (Backend + Dashboard or _none_), Dependencies.
3. Create the GitHub issue
gh issue create \
--title "LKPR-N: <title>" \
--label "S:Proposal,P2: medium" \
--body "$(cat backlogs/LKPR-N-<slug>.md)" \
--repo Jessinra/Lorekeeper
Important: GitHub label format has a space between colon and value (e.g. P2: medium, not P2:medium).
4. Add GitHub issue number to frontmatter
After creating the issue, add its number to the frontmatter. The pre-commit hook validates this field — it must be the numeric ID, not the full URL:
github_issue: 211 # number only, not "https://github.com/..."
Then run Prettier — the pre-commit hook checks formatting and will reject unformatted files:
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 · 137 lines · 41 tokens per session scan A 6dde08022a28
proposal-filing is a skill published in the GitHub repository Jessinra/Lorekeeper (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,159 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
development-scheduler
A workflow for coordinating multi-role coding work through Herdr, a task scheduler, and repo-harness sessions. It assigns implementation, review, and handoff tasks while checking permissions and evidence.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.