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/synkraai/aiox-core/smnpx skills add SynkraAI/aiox-core --skill smgit clone --depth 1 https://github.com/SynkraAI/aiox-coreWrote 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/synkraai/aiox-core/sm)<a href="https://agentmods.dev/skills/synkraai/aiox-core/sm"><img src="https://agentmods.dev/badge/skills/synkraai/aiox-core/sm.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 | $0.00049 | $0.03013 |
| Opus 5 | $0.00024 | $0.01507 |
| Sonnet 5 | $0.00010 | $0.00603 |
| Haiku 4.5 | $0.00005 | $0.00301 |
Grade A, and why
aiox-sm 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 4d 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.
- 4d ago First seen · 296 lines · 49 tokens per session scan A 7f586450bdbd
aiox-sm is a skill published in the GitHub repository SynkraAI/aiox-core (3,103 stars, last pushed yesterday), with no licence file. It adds 49 tokens to every session and 3,013 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-30.
Other skills, from other repositories
devloop
Goal-driven development loop — define objective, write rules with key-results, verify visually, sync to issue tracker.
sprint-planning
Plan implementation sprints with story selection, goal definition, and execution ordering.
sprint-contract
Negotiate a pre-code contract between generator and evaluator personas that defines what "done" means before any code is written. Turns fuzzy specs into a testable target the evaluator can hold the generator to.
ergo-backlog-planning
Shape and execute multi-step work with the Ergo CLI, a repository-local backlog management tool. Use to plan software development, documentation, or general knowledge work as a series or graph of well-defined tasks. Use to define dependencies within that task backlog. Use to group tasks into epics when needed. Skip…
sprint-plan
Start the Plan phase of the SPARK loop: the Engineering Manager turns an approved spec into a technical plan — architecture decision with rejected alternatives, ordered task breakdown with definitions of done, test strategy and risks. Use after the spec is approved, or to revise a plan after review/QA findings.
sprint-planning
Facilitates sprint planning with security debt baked in: capacity planning from rolling velocity, risk-weighted prioritization balancing feature value against security debt, commitment sizing, and a DevSecOps definition of done. For writing or refining the stories themselves, use user-story-writing instead. Triggers…