agentmods.dev

Lorekeeper javascript.instructions.md

Instructions for reviewing the JavaScript used by a static dashboard, a web page that displays project data. They cover shared helpers, readable data loading, error handling, and checks for stale or repeated requests.

In plain words
What is it for?
Use them when changing dashboard loading or display behavior, especially to review API-helper reuse, DOM updates, promise failures, dependencies, race conditions, and rendered behavior.
Why use it?
They help keep the dashboard's existing no-framework code understandable and prevent silent failures or unnecessary network calls.

Instructions file for GitHub Copilot

4 29d ago A scan 177 tokens original Apache-2.0
View the source file Jessinra/Lorekeeper
Install

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.

agentmods
npx agentmods add instructions/jessinra/lorekeeper/javascript
Clone the repo
git clone --depth 1 https://github.com/Jessinra/Lorekeeper

Made for: GitHub Copilot.

Per session 177 This file is loaded in full into every session.
When invoked 177 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00177 $0.00177
Opus 5 $0.00088 $0.00088
Sonnet 5 $0.00035 $0.00035
Haiku 4.5 $0.00018 $0.00018

Measured yesterday against content hash 7d5a16280ae6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Lorekeeper javascript.instructions.md 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 yesterday.

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.

.github/instructions/javascript.instructions.md · 30 lines

What it actually says

Dashboard JavaScript Guidelines

Scope

Apply these rules to the static dashboard JavaScript.

Review focus

  • Reuse the existing API helper and shared utilities.
  • Avoid raw fetch wrappers when the project already has a helper.
  • Keep DOM updates and data loading easy to follow.
  • Prefer small modules over ad hoc duplication.
  • Avoid console noise and unhandled promise failures.

UI behavior

  • Preserve the existing no-framework dashboard approach.
  • Keep error states visible and user-facing.
  • Do not introduce new dependencies for small UI changes.
  • Watch for stale state, race conditions, and repeated network calls.

Testing / verification

  • If a change affects the dashboard flow, check the rendered behavior.
  • Keep code consistent with the current style and naming in the static JS tree.
Changes

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.

  1. yesterday First seen · 30 lines · 177 tokens per session scan A 7d5a16280ae6

Subscribe to this mod's changes

Lorekeeper javascript.instructions.md is an instructions file published in the GitHub repository Jessinra/Lorekeeper (4 stars, last pushed 29d ago), licensed Apache-2.0. It adds 177 tokens to every session, about $0.0009 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.

Analytics and metricsCode reviewMemory and contextagent-memoryagentic-aiagentic-workflowsai-memoryclaude-codeclaude-code-memory
Related

Other instructions, from other repositories

hindsight CLAUDE.md

Instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.

vectorize-io/hindsight · 4,846 tokens

EverOS CLAUDE.md

Claude Code instructions for EverMind-AI/EverOS, covering everos — md-first memory extraction framework, quick commands, architecture, engineering practices and branch strategy.

EverMind-AI/EverOS · 1,056 tokens

plur CLAUDE.md

Instructions for plur-ai/plur, covering claude.md, what is plur, development, package dependency and version bumps.

plur-ai/plur · 4,509 tokens

dense-mem AGENTS.md

Instructions for markhuangai/dense-mem, covering dense-mem repository guidance, project context, architecture decision records, current stack and target architecture.

markhuangai/dense-mem · 2,447 tokens

Meterless AGENTS.md

Instructions for Meterless/Meterless, covering agent instructions for meterless, routing table, isolation rule, repo-wide rules and non-coding agents.

Meterless/Meterless · 456 tokens

open-bridge AGENTS.md

Instructions for bks-lab/open-bridge, covering the bridge — agent instructions, required reading, session start detection (automatic), theme and agents.

bks-lab/open-bridge · 8,154 tokens