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 nocodework/ai-context-kit --skill personal-contextgit clone --depth 1 https://github.com/nocodework/ai-context-kitWrote 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/nocodework/ai-context-kit/personal-context)<a href="https://agentmods.dev/skills/nocodework/ai-context-kit/personal-context"><img src="https://agentmods.dev/badge/skills/nocodework/ai-context-kit/personal-context/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/nocodework/ai-context-kit/personal-context"><img src="https://agentmods.dev/badge/skills/nocodework/ai-context-kit/personal-context.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.00097 | $0.01183 |
| Opus 5.5 | $0.00039 | $0.00473 |
| Sonnet 5.5 | $0.00019 | $0.00237 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
personal-context 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
personal-context — build a reusable "about me" file
Your job is to interview the user briefly and write a clean personal-context.md they can feed into any AI tool (ChatGPT/Claude/Gemini Projects, CLAUDE.md, Cursor rules, or just pasted into a chat).
If personal-context.md already exists in the current directory, read it first, give the user a two-line summary, and ask what has changed — then update those parts and refresh the Last updated line. Don't re-run the interview from scratch and don't overwrite their file without confirmation.
How to run the interview
- Ask in small batches (3–5 questions at a time), not all at once. Keep it conversational.
- Interview and write the file in the user's language — if they write in Polish, ask and write in Polish.
- Use what you already know (their messages, the repo, git config) to pre-fill answers and just ask them to confirm — don't ask what you can infer.
- Sections 1, 3 and 7 (identity, day to day, how AI should help) are the core — cover them first, then offer the rest; a file with just the core is already useful, so let the user stop there if they want.
- On "I don't know": give one concrete example answer; if they still don't know, skip the point and move on — don't push.
- After the core questions, proactively suggest gaps: "Here's what would also make this more useful — want to add any?" and name 2–4 specific things they haven't covered.
- Keep it respectful of privacy. Personal details (age, location) are optional — offer, never insist.
- When they're done, write the file (see Output). Keep their own words and tone where possible.
What to cover
- Identity — name, role/title, company or what they do, location and languages (optional).
- Background — a 2–3 sentence bio, years of experience, domains of real expertise, a couple of notable wins.
- Day to day — main responsibilities, what they're focused on right now, current projects.
- How they work — working style, how they make decisions, tools they rely on, strengths, and what they prefer to delegate or avoid.
- Communication & voice — tone (formal/casual), who they usually write for, words/phrases they like and ones they avoid.
- Goals — what they're working toward (next 6–12 months and longer), what "success" looks like.
- How AI should help them — preferred answer style and format, level of detail, things AI should always do, and things it should never do.
- Anything else — an open prompt for what they want any AI to know about them.
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 · 55 lines · 97 tokens per session scan A 7d26104f8708
personal-context is a skill published in the GitHub repository nocodework/ai-context-kit (35 stars, last pushed 11d ago), licensed MIT. It adds 97 tokens to every session and 1,183 once invoked, about $0.0004 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-30.
Other skills, from other repositories
faf-expert
Expert in .faf (Foundational AI-context Format) files for persistent project context. Use when working with .faf files, project DNA, CLAUDE.md bi-sync, faf-cli commands, MCP server configuration, or AI-readiness scoring (0-100%). Updated for v2.8.0 Tool Visibility System.
obsidian
Read, search, and create Markdown notes inside an Obsidian vault on disk.
handoff
Write one self-contained goal that a fresh session can continue from. Use when context is running out, before clearing a session, when usage passes 95% on a long run, or when asked for a handoff.
init
Set up Dory in this repo by exploring it, creating wiki/ from the template, and connecting the usage statusline. Use when a project has no wiki/ yet, or when asked to set up Dory.
waky-waky
Context-restoration ritual for new sessions. Use when the user says "waky waky", "wake up the swarm", "reincarnate", "reincarnate the swarm", or "restore context". Loads the Constitution, identity, active handoffs, and per-WIP state so a fresh session picks up where the last one ended.
sr:save
Phase 9 of the SRS workflow. Saves all project context to context/ files so future Claude sessions can resume without re-reading the full SRS.