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 srinivasan-sundaresan95/orihime --skill orihime-setupgit clone --depth 1 https://github.com/srinivasan-sundaresan95/orihimeWrote 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/srinivasan-sundaresan95/orihime/orihime-setup)<a href="https://agentmods.dev/skills/srinivasan-sundaresan95/orihime/orihime-setup"><img src="https://agentmods.dev/badge/skills/srinivasan-sundaresan95/orihime/orihime-setup/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/srinivasan-sundaresan95/orihime/orihime-setup"><img src="https://agentmods.dev/badge/skills/srinivasan-sundaresan95/orihime/orihime-setup.svg" alt="Reviewed on agentmods" width="80" 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.00090 | $0.01277 |
| Opus 5 | $0.00045 | $0.00639 |
| Sonnet 5 | $0.00018 | $0.00255 |
| Haiku 4.5 | $0.00009 | $0.00128 |
Grade A, and why
orihime-setup 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 11d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 11d ago First seen · 185 lines · 90 tokens per session scan A b74fa2ae3833
orihime-setup is a skill published in the GitHub repository srinivasan-sundaresan95/orihime (1 stars, last pushed 3mo ago), with no licence file. It adds 90 tokens to every session and 1,277 once invoked, about $0.0005 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
dekko-orient
Use dekko's tools instead of grep/Read whenever a repo has a .dekko/ directory — not just at session start. Trigger on any "find/locate/understand this symbol," "what does this file/dir contain," "what will this change break," or "read this file" impulse. dekko has already parsed and indexed the repo; grepping or…
dekko-daemon
Start dekko's background daemon before a session that will run many bare dekko CLI commands via Bash (not the MCP tools) against a large or medium repo. Trigger when you're about to run several dekko CLI invocations in a row on the same repo — a long refactor loop, a batch of query/search/outline calls, or a…
dekko-notes
Read and write dekko's symbol-anchored notes in any repo with a .dekko/ directory. Trigger every time you pull a symbol's context (querysymbol, getcontextpack, dekko query/context), right after a non-obvious change, and right after any rename/move/signature edit (to sweep orphaned notes). Notes are durable, committed…
dekko-verify
Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…
dekko-review-context
Give a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (this repo's open-agent-hub:review//review, or an equivalent in another environment) against a diff in a repo with a…
release-tag
Cut and publish a codeweb release end-to-end — prep the version/changelog file ecosystem, land it on main, push the vX.Y.Z tag, and let the tag-triggered workflow publish the GitHub Release. Use when asked to "cut a release", "tag a release", "publish vX.Y.Z", "do the release", or "ship version X".