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/sushuheng/obshare-cli/uploadnpx skills add SuShuheng/obshare-cli --skill uploadgit clone --depth 1 https://github.com/SuShuheng/obshare-cliWhat 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.00037 | $0.00316 |
| Opus 5 | $0.00018 | $0.00158 |
| Sonnet 5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
upload 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 2d 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.
What it actually says
obshare-cli upload
Upload one Markdown file to Feishu.
Syntax
conda run -n obsd obshare-cli upload <file>
conda run -n obsd obshare-cli upload <file> --public --allow-copy --allow-download
conda run -n obsd obshare-cli --json upload <file>
Examples
conda run -n obsd obshare-cli upload note.md
conda run -n obsd obshare-cli upload /path/to/note.md --public
conda run -n obsd obshare-cli upload note.md --allow-copy --allow-download
conda run -n obsd obshare-cli --json upload note.md
Result
Successful output includes:
- Document title
- Document token
- Feishu URL
- Applied permission flags
- Upload time
Notes
- Required config must be complete before upload.
- Upload history is saved to
~/.obshare/history.json. --jsonis a global flag and must appear beforeupload.- If you rely on Mermaid rendering through the companion plugin, configure the optional Obsidian bridge settings first.
- In
V0.2.0, the Obsidian companion plugin calls this command as the backend for direct note sharing.
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.
- 2d ago First seen · 44 lines · 37 tokens per session scan A 4f2a7575327e
upload is a skill published in the GitHub repository SuShuheng/obshare-cli (2 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 316 once invoked, about $0.0002 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
notion-artifact-capture
Use when a user says “save to Notion” for research, reports, drafts, references, or generated artifacts and wants a reusable default destination. Bootstraps a generic Notion AI Output Library under a user-created shared parent page, saves typed metadata and optional Markdown, verifies every write through the live API…
google-workspace
Gmail, Calendar, Drive, Contacts, Sheets, and Docs — through Hermes-managed OAuth and a thin CLI wrapper. When gws is installed, the skill uses it as the execution backend for broader Google Workspace coverage; otherwise it falls back to the bundled Python client implementation.
notion
Notion API + ntn CLI: pages, databases, markdown, Workers.
coding-worktree-recovery
Use this skill when coding-agent work is interrupted, an agent exits without a clean commit, multiple controllers target the same checkout, or the checkout produces inconsistent file/Git behavior.
browser-harness-authoring
Use when mapping a repeatable website workflow into a verified Hermes skill so later runs can follow known steps instead of rediscovering the site. Surveys browser compatibility, semantic targets, failure modes, recovery paths, decision gates, and expiry using dummy data and no irreversible submissions.
obsidian-memory-architecture
Use when designing, setting up, or maintaining an Obsidian vault as Hermes Agent's durable knowledge layer. Routes facts, conversation history, documents, procedures, and daily logs to the correct Hermes or vault system without duplicating everything into the prompt.