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 CocoRoF/Geny --skill whiteboard_react_to_sharegit clone --depth 1 https://github.com/CocoRoF/GenyWrote 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/cocorof/geny/whiteboard_react_to_share)<a href="https://agentmods.dev/skills/cocorof/geny/whiteboard_react_to_share"><img src="https://agentmods.dev/badge/skills/cocorof/geny/whiteboard_react_to_share.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.00052 | $0.01118 |
| Opus 5 | $0.00026 | $0.00559 |
| Sonnet 5 | $0.00010 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
whiteboard-react-to-share 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 6d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Whiteboard: React to Share — React naturally to a share
Use this skill when the user has explicitly shared a note/image/screen capture.
Two trigger forms
- Immediate trigger — a synthetic prompt for a single turn that starts with
[USER_SHARED] {json...}.- Read the JSON's
title,kind,source_filename,excerpt,seen_before, andattachments_count, and react naturally.
- Read the JSON's
- Persistent context — the
[Spotlight Context]block is included in the system prompt every turn. Active items persist until they expire (~30 minutes).
Reaction Ladder
Decide in order:
Step 1: Check seen_before
- If
seen_before == true: "you shared that [title] again that we saw last time" — don't act as if you're seeing it for the first time. Pick up the prior context. - If
seen_before == false: take it as new info, e.g. "oh, this is material/an image I haven't seen before".
Next to each item in the [Spotlight Context] block there is a marker like ⚑ previously seen — 3× read, 7× injected or ⚑ first time / 처음 보는 자료. Ignoring this marker breaks the persona.
Step 2: Handle attachments
| Situation | Action |
|---|---|
No attachment + sufficient excerpt |
Voice your opinion from the excerpt alone. No extra tool call needed. |
| Image attachment + your model is vision-capable | It's attached to the system prompt as an image content block → look at it directly and react. |
| Image attachment + your model is NOT vision-capable | You must call whiteboard_describe(capture_id="...") and react based on that caption. Don't guess at the image. |
| Body appears to have many links (lots of URLs in the excerpt) | Call whiteboard_extract_links(filename="...") → point out just 1–2 key URLs to the user. |
The capture_id is in the capture_id field of the [USER_SHARED] payload.
Step 3: Read if you need more of the body
If you feel the excerpt is insufficient (e.g. a decision/summary/number looks truncated):
- For a note in User Opsidian →
opsidian_read(filename="...") - For a note in Curated Knowledge →
knowledge_read(filename="...")
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.
- 6d ago First seen · 88 lines · 52 tokens per session scan A fa9f61852942
whiteboard-react-to-share is a skill published in the GitHub repository CocoRoF/Geny (10 stars, last pushed 8d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,118 once invoked, about $0.0003 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
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
cross-task-learner
Enable agent loops to learn from similar past tasks and share patterns across loops.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
reflection-injection
Inject relevant past reflections into agent context at iteration start so agents learn from prior mistakes without repeating them.