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 juspay/xyne-spaces --skill evidence-citationsgit clone --depth 1 https://github.com/juspay/xyne-spacesWrote 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/juspay/xyne-spaces/evidence-citations)<a href="https://agentmods.dev/skills/juspay/xyne-spaces/evidence-citations"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/evidence-citations/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/juspay/xyne-spaces/evidence-citations"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/evidence-citations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00344 |
| Opus 5.5 | $0.00013 | $0.00138 |
| Sonnet 5.5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
evidence-citations 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 2mo 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
Evidence and citations
Every non-obvious claim carries a path/to/file.ext:LINE anchor. This is also
what closes a path in an understanding run — a finding recorded without one is
downgraded to an open conjecture, so an uncited explanation is not merely weak,
it does not count.
- Cite the line that actually shows the behaviour: the write, the query, the branch. Citing the type definition proves the entity exists, which was never in question.
- Never cite a file you did not open. A plausible path is the easiest thing in this job to invent and the most expensive thing for a reader to discover is wrong.
- Prefer two anchors that disagree over one that is tidy. "Written here, but also mutated here" is the finding.
- When you searched and found nothing — no writer, no reader, no caller — say so explicitly and give the search you ran. An unreferenced table is a real and useful result, not a failure to look.
Separate verified from inferred in the document itself. Mark inference as inference ("appears to be", "no caller found in this repo") and keep it out of the summary lines a reader will quote. In the HTML, render anchors in monospace so they are visibly checkable, and keep the repo, branch and commit in the header so a stale citation can be dated rather than merely doubted.
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.
- 2mo ago First seen · 30 lines · 33 tokens per session scan A 4a01da2eaca9
evidence-citations is a skill published in the GitHub repository juspay/xyne-spaces (827 stars, last pushed today), licensed Apache-2.0. It adds 33 tokens to every session and 344 once invoked, about $0.0001 per session on Opus 5.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
git-workflow-branching
When creating, updating, and merging code in a collaborative version control environment.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
queues-jobs
Implement reliable asynchronous jobs and message consumers with explicit delivery, retry and shutdown semantics. Use when adding BullMQ or another established queue, background processing or scheduled work; enqueue success is not job completion.