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 spec-taskgit 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/spec-task)<a href="https://agentmods.dev/skills/juspay/xyne-spaces/spec-task"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/spec-task/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/spec-task"><img src="https://agentmods.dev/badge/skills/juspay/xyne-spaces/spec-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 Excessive Agency · line 210 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.
- medium Excessive Agency · line 413 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.
- medium Excessive Agency · line 444 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.00028 | $0.02912 |
| Opus 5.5 | $0.00011 | $0.01165 |
| Sonnet 5.5 | $0.00006 | $0.00582 |
| Haiku 4.5 | $0.00003 | $0.00291 |
Grade A, and why
Ticket Specs 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 1mo 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 — 592 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Xyne Spaces Ticket Specification
Use this skill when creating, generating, regenerating, or updating a Xyne Spaces ticket specification.
The purpose of the Specification is to capture the requirement intent so that:
- a developer can understand what is expected,
- a PR reviewer can understand what was requested,
- and the implementation can later be reviewed against that requirement.
The Specification must come from requirement context and user clarification.
Do not generate requirement intent merely by describing the implementation.
Specification sections
Use these headings exactly.
Required
Problem statement
Describe what is wrong, missing, or needed and who or what is affected.
The Problem statement should explain why this work exists.
Solutioning
Describe the expected functional behaviour after the change is shipped.
Focus on what must be true functionally, not how the developer should implement it.
Test cases
Describe the observable scenarios that confirm the requirement works.
Test cases should make it possible for a developer or reviewer to understand what behaviours need to succeed.
Optional
Implementation details
Technical details, constraints, or implementation context that are useful to the developer or reviewer.
Do not require this section when there is nothing meaningful to record.
Out of scope
Anything explicitly excluded from this ticket.
Do not invent non-goals simply to populate this section.
Before the interview
Before creating or regenerating a Specification, first understand the requirement context.
If this is an existing ticket:
- Fetch the ticket using
spaces-tickets. - Read:
- ticket title,
- ticket type, when available,
- existing description,
- existing Specification, when present,
- other relevant requirement context available with the ticket.
- Use this information to understand what the ticket is about.
- Use it to formulate better and more relevant clarification questions.
- Do NOT create or update the Specification yet.
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.
- 1mo ago First seen · 592 lines · 28 tokens per session scan A a1439d1133b8
Ticket Specs is a skill published in the GitHub repository juspay/xyne-spaces (820 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 2,912 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-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
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…