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/ripemangobox/bite/notes-export-share-versionnpx skills add RipeMangoBox/BITE --skill notes-export-share-versiongit clone --depth 1 https://github.com/RipeMangoBox/BITEWrote 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/ripemangobox/bite/notes-export-share-version)<a href="https://agentmods.dev/skills/ripemangobox/bite/notes-export-share-version"><img src="https://agentmods.dev/badge/skills/ripemangobox/bite/notes-export-share-version.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 | $0.00067 | $0.00687 |
| Opus 5 | $0.00034 | $0.00344 |
| Sonnet 5 | $0.00013 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
notes-export-share-version 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 3d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Share Note Export
What this skill does
Converts an internal research note into a shareable Markdown note for external readers. This is an export-only skill: it creates a local share artifact and should not be treated as a service data write.
Default behavior:
- keep the source note unchanged
- create a share version in the same directory
- remove internal knowledge-base traces
- rewrite paper mentions as public Markdown links with short visible names
- add a short abstract at the top
- append a unified
Referencessection at the end - run a markdown lint check after edits
When to use
Use this skill only when the user explicitly asks for a share version, such as:
- "make a share version"
- "export a share draft"
- "version for external readers"
- "hide knowledge base traces"
- "clean internal notes into a shareable version"
Do not apply automatically for normal note editing.
Quick workflow
Copy this checklist and follow it in order:
Share Export Progress:
- [ ] Step 1: Read the source note
- [ ] Step 2: Generate a content-driven `_share.md` filename
- [ ] Step 3: Replace internal paper references with public Markdown links
- [ ] Step 4: Remove internal traces and rewrite internal wording
- [ ] Step 5: Add a short abstract
- [ ] Step 6: Add or refresh a unified `References` section
- [ ] Step 7: Validate markdown formatting
Core output rules
1. Never overwrite the source note by default
Treat the source note as the internal working version. Create a separate share version unless the user explicitly asks to overwrite.
2. Output location
Write the share version to the same directory as the source file.
3. Filename rule
Use a content-driven filename:
- remove leading dates like
2026-04-02_ - remove temporary suffixes like
copy,final,v2,draft - keep only the topic-defining slug
- use lowercase words joined by
- - end with
_share.md
Example:
2026-04-02_vq-codebook-motion-text-alignment-survey copy.md→vq-codebook-motion-text-alignment-survey_share.md
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 99 lines · 67 tokens per session scan A f83623117139
notes-export-share-version is a skill published in the GitHub repository RipeMangoBox/BITE (60 stars, last pushed 21d ago), licensed MIT. It adds 67 tokens to every session and 687 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-30.
Other skills, from other repositories
compile-wiki
Merge source summaries into durable concept pages with backlinks, index entries, and explicit open questions.
ingest-sources
Review newly ingested raw sources and draft or update source summary notes in notes/Sources/.
qa-agent
Answer questions from the vault, then file durable insights back into the knowledge base.
research-workflow
Manage resumable research runs under research/ and coordinate the collect, review, report, import, and archive steps.
lint-heal
Scan the vault for contradictions, unsupported claims, structural weaknesses, and missing pages, then repair what is safe.
render-output
Convert vault content into downstream outputs like memos, reports, slide outlines, diagrams, and plot specifications.