Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AtlasOmnia/hermes-custom-packnpx agentmods add skills/atlasomnia/hermes-custom-pack/notion-artifact-captureWrote 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/atlasomnia/hermes-custom-pack/notion-artifact-capture)<a href="https://agentmods.dev/skills/atlasomnia/hermes-custom-pack/notion-artifact-capture"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/notion-artifact-capture/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/atlasomnia/hermes-custom-pack/notion-artifact-capture"><img src="https://agentmods.dev/badge/skills/atlasomnia/hermes-custom-pack/notion-artifact-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Agent Snooping · line 102 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Rogue Agent · line 133 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 95 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00082 | $0.03284 |
| Opus 5 | $0.00041 | $0.01642 |
| Sonnet 5 | $0.00016 | $0.00657 |
| Haiku 4.5 | $0.00008 | $0.00328 |
Grade A, and why
notion-artifact-capture 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 12d 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notion Artifact Capture
Overview
Turn “save to Notion” into a reliable reusable workflow. On first use, the user creates one blank Notion parent page and shares it with a Notion integration. Hermes then creates a child database named AI Output Library, stores its destination IDs in a local non-secret config file, and uses that database for later research, reports, drafts, references, and project artifacts.
This skill extends the general notion skill:
notionowns API mechanics and current Notion behavior;- this skill owns the artifact schema, first-run bootstrap, destination convention, save defaults, and verification contract.
The published skill contains no workspace IDs, personal paths, credentials, private hosts, or business-specific schema. Each installation discovers and stores its own destination.
When to Use
Use when:
- the user says “save to Notion” without naming a destination;
- research, reports, substantial drafts, source collections, or generated project artifacts should be easy to find later;
- a user wants one standard Notion table rather than deciding where every output belongs;
- a new installation needs to create and configure its output library;
- an existing save must be verified by reading the created page back through the API.
Do not use when:
- the user names another Notion page or database—honor the explicit destination;
- the content belongs in Hermes memory, session history, source control, or a task manager instead;
- the artifact contains secrets that should not be stored in Notion;
- the user asks only to edit an ordinary Notion page—use the general
notionskill; - a final external publish, payment, deletion, or irreversible action is involved without explicit authorization.
Architecture
User creates blank parent page
│
▼
Shares page with Notion integration
│
▼
bootstrap_library.py
├─ creates AI Output Library database
├─ creates typed property schema
├─ reads schema back from Notion
└─ writes local destination config
│
▼
“Save to Notion”
│
▼
save_artifact.py
├─ loads local destination
├─ fetches live schema
├─ creates typed page + optional Markdown
└─ reads page back and verifies title
What ships with it
4 files 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.
- 12d ago First seen · 341 lines · 82 tokens per session scan A 8bc9f969ffbc
notion-artifact-capture is a skill published in the GitHub repository AtlasOmnia/hermes-custom-pack (56 stars, last pushed 28d ago), licensed MIT. It adds 82 tokens to every session and 3,284 once invoked, about $0.0004 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
obshare-cli
Use when setting up obshare-cli 0.2.0, reviewing available commands, or choosing the right command for config, upload, permission, history, delete, and the plugin-first direct-share workflow.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
macos-storage-management
Safely reclaim local Mac storage without mistaking cloud placeholders for resident data, losing File Provider content, or flattening metadata onto an incompatible external filesystem.
vault-organization
Audit and reorganize the user's Obsidian vault. Run when asked to organize, clean up, or audit the vault structure — or to set up a sensible structure for a new/empty vault.
apple-reminders
Use remindctl to manage Apple Reminders directly from the terminal. Tasks sync across all Apple devices via iCloud.