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 rusty4444/shiori-mcp --skill skillgit clone --depth 1 https://github.com/rusty4444/shiori-mcpWrote 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/rusty4444/shiori-mcp/skill)<a href="https://agentmods.dev/skills/rusty4444/shiori-mcp/skill"><img src="https://agentmods.dev/badge/skills/rusty4444/shiori-mcp/skill.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.00025 | $0.00394 |
| Opus 5 | $0.00013 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
shiori 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.
What it actually says
Shiori MCP Skill
Use this skill when the user asks Hermes to connect to or automate Shiori.
Setup
Configure the MCP server with:
{
"mcpServers": {
"shiori": {
"command": "shiori-mcp",
"env": {
"SHIORI_BASE_URL": "https://shiori.example.com",
"SHIORI_USERNAME": "your-username",
"SHIORI_PASSWORD": "your-password"
}
}
}
}
Alternatively provide SHIORI_SESSION_ID to skip login.
Tool selection
- Health/auth:
shiori_health_check - Reading/search:
shiori_list_bookmarks,shiori_search_bookmarks,shiori_get_bookmark,shiori_get_bookmark_by_url - Capture/edit/delete:
shiori_add_bookmark,shiori_update_bookmark,shiori_update_bookmark_fields,shiori_delete_bookmark,shiori_delete_bookmarks - Tags:
shiori_list_tags,shiori_rename_tag - Accounts:
shiori_list_accounts
Pitfalls
- Shiori legacy API tags are objects like
{ "name": "Interesting" }, not bare strings. The add tool converts comma-separated tags for you. - The update API expects a full bookmark object including
id; fetch the bookmark first, then edit the JSON. - The new API v1 is still in development; this server targets the documented legacy
/api/*endpoints for stability.
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 · 50 lines · 25 tokens per session scan A 307bcefb5722
shiori is a skill published in the GitHub repository rusty4444/shiori-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 394 once invoked, about $0.0001 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
karakeep
Official skill for how to use karakeep (the bookmark manager) and interact with it programmatically.
vulnerability-triage
Reference vocabulary for interpreting vulnerability findings — detector-vs-impact distinction, severity anchoring on demonstrated evidence, the eleven-item interpretation rubric, delegation transparency, primitive-extent scaling, the disqualifier taxonomy (D-0..D-4), CVSS Achievable / Environmental framing…
harness-design-fuzzing
Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…
memory-safety-c-cpp
Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…
gmail-query-syntax
Reference for Gmail's search query syntax — operators like is:sent, newerthan:, from:, has:attachment, label:, and how they compose. Read this when constructing a Gmail search query string for the googleworkspace.gmailsearchmessages Code Mode call, especially when filtering by sent vs received, recency, sender, or…
email-formatting
Markdown formatting conventions for email summary documents — heading depth, list style, line length, emoji policy, and a mandatory provenance footer. Read this when producing a markdown report that summarizes one or more email messages so the output matches the project's house style.