Borrowing it
Nothing to install: this file belongs to amirkiarafiei/open-scholar-peer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/amirkiarafiei/open-scholar-peer/main/.agents/skills/kia-context-sync/SKILL.mdgit clone --depth 1 https://github.com/amirkiarafiei/open-scholar-peerWrote 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/amirkiarafiei/open-scholar-peer/kia-context-sync)<a href="https://agentmods.dev/skills/amirkiarafiei/open-scholar-peer/kia-context-sync"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/open-scholar-peer/kia-context-sync/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/amirkiarafiei/open-scholar-peer/kia-context-sync"><img src="https://agentmods.dev/badge/skills/amirkiarafiei/open-scholar-peer/kia-context-sync.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.00088 | $0.00882 |
| Opus 5.5 | $0.00035 | $0.00353 |
| Sonnet 5.5 | $0.00018 | $0.00176 |
| Haiku 4.5 | $0.00009 | $0.00088 |
Grade A, and why
kia-context-sync 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kia-context-sync — catch the context up
The agent is supposed to keep these files current as it works. This is for when it did not, or when somebody wants a deliberate pass before handing the project over.
Step 1 — find the gap
git log --oneline --no-merges -30
git log -1 --format=%ad -- kia-context/ # when the context last moved
git diff --stat HEAD~10..HEAD -- . ':!kia-context' ':!docs'
Compare what the code did against what the files say happened. The gap is the work.
Step 2 — update the logs
logs/PROGRESS.md — tick the deliverables that are genuinely done, and write the Report for any
milestone that closed. Verify against the acceptance criteria; do not tick on the strength of a commit
message. If something is half-finished, say so rather than ticking it.
logs/BRAINSTORM.md — apply the entry test before writing anything:
An entry earns its place when an alternative was rejected, or when a measurement changed our minds.
Most of what happened does not qualify. A bug fix is not a decision. A refactor with no choice in it is not a decision. If nothing in this window qualifies, write nothing — that is the correct outcome, not a failure of the pass.
Step 3 — correct the specs where the build moved past them
Only where they are now wrong, not merely thin.
ARCHITECTURE.md— did the stack, the layout or a structural fact change?DESIGN.md— did tokens or components change in the interface but not here?MANIFESTO.md— a rule almost never changes. If one did, it was a decision, so it needs aBRAINSTORM.mdentry too. Never renumber.
Step 4 — the seven rules
Walk them. Each one fails silently, which is why they need a deliberate check.
- Nothing renumbered. Milestone, decision and rule numbers are permanent.
- No dead references. If anything was renamed or moved, grep the old name:
grep -rn "OldName" . --exclude-dir=node_modules --exclude-dir=.git - No rule stated in two files. One states it, the rest link to it.
- Nothing appended to a file whose
status:isclosed. INDEX.mdstill matches what the files actually contain. If it disagrees, the index is the bug.- Frontmatter is current —
covers,statusandlast_updatedon every file you touched. - Every number is measured. Re-run the command behind any count you carry forward, or drop it.
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 · 71 lines · 88 tokens per session scan A 67c5926db615
kia-context-sync is a skill published in the GitHub repository amirkiarafiei/open-scholar-peer (51 stars, last pushed 5d ago), licensed MIT. It adds 88 tokens to every session and 882 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-09-12.
Other skills, from other repositories
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
knowledge-meeting-ingest
Ingest meeting transcripts from any recorder into Knowledge with attendee enrichment, source notes, supported decisions and commitments, and verification of substance and sequence. Summary-only input is not a verified meeting ingestion.
knowledge-automation
Create scheduled Knowledge ingestion automations with a verified worker, private-vault authority, and an end-to-end scheduled run. Use when asked to schedule or repair recurring ingestion from any source.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
md-hive-sync
Munder Difflin hive sync — runs the start-of-task hive protocol steps: reads memory.md, checks inbox/ for new messages, and reminds you to record durable facts in memory.md and write coordination files before ending. Use when asked to "sync with the hive", "check my inbox", "hive status", or "hive sync". Proactively…
commonly
You are a member of a Commonly workspace — a shared space where humans and AI agents from any origin collaborate in pods (chat rooms with memory). Use this whenever you are connected to Commonly via the commonly MCP tools: to read what's happening, post, remember things across sessions, react, DM other agents, and…