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 agentmods add skills/kleosr/kleosrules/nownpx skills add kleosr/kleosrules --skill nowgit clone --depth 1 https://github.com/kleosr/kleosrulesWrote 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/kleosr/kleosrules/now)<a href="https://agentmods.dev/skills/kleosr/kleosrules/now"><img src="https://agentmods.dev/badge/skills/kleosr/kleosrules/now.svg" alt="Measured on agentmods" 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.00032 | $0.00216 |
| Opus 5 | $0.00016 | $0.00108 |
| Sonnet 5 | $0.00006 | $0.00043 |
| Haiku 4.5 | $0.00003 | $0.00022 |
Grade A, and why
now 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 today.
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.
What it actually says
Now
Persist state in the repo. Cursor chats die.
Path
One file: NOW.md at repo root.
Resume
- Read
NOW.mdif it exists. - Re-run listed TOOLCHAIN/CI commands before claiming prior work is green.
- Do one Next action unless the user said autopilot/
sigue. - Do not re-discover the whole codebase; open only paths listed or needed.
Update
Keep Now, State, Limits, Proof, Next. Compact into Archived when active sections exceed ~150 lines. English labels. No secrets.
Rules
- Assessment-only until the user asked for changes (per
agent.mdc). - Never invent residual features; append open items here.
- Pair with testing for feature execution; debugging if Next is ambiguous.
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.
- today Changed · -1 lines · -10 tokens per session 28c35278f66f
- 5d ago First seen · 33 lines · 42 tokens per session scan A 7dfd5f33688a
now is a skill published in the GitHub repository kleosr/kleosrules (2 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 216 once invoked, about $0.0002 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
checkpoint
Save a session checkpoint — what was done, what's next, any blockers.
resume
Resume from last checkpoint — load full context and continue where you left off.
note
Quick note — save a decision, observation, or thought to persistent memory.
researcher-context-compression
Summarizes project state, updates architecture, compresses context. Use when TRIGGERRESEARCHER fires (every 20 tasks) or when context has grown too large.
memory-awareness
Proactive memory usage for continuity across sessions. Use when a memory MCP is available — this skill governs when to automatically query and store memories, ensuring context persists between conversations. Triggers on task start, project context switch, architectural decision, complex bug resolution, and milestone…
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.