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/nusabyte-my/jebat-core/cortex-reasoningnpx skills add nusabyte-my/jebat-core --skill cortex-reasoninggit clone --depth 1 https://github.com/nusabyte-my/jebat-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/nusabyte-my/jebat-core/cortex-reasoning)<a href="https://agentmods.dev/skills/nusabyte-my/jebat-core/cortex-reasoning"><img src="https://agentmods.dev/badge/skills/nusabyte-my/jebat-core/cortex-reasoning.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.00015 | $0.00234 |
| Opus 5 | $0.00008 | $0.00117 |
| Sonnet 5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
cortex-reasoning 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 5d 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.
- 5d ago First seen · 47 lines · 15 tokens per session scan A 0e30c9a2a486
cortex-reasoning is a skill published in the GitHub repository nusabyte-my/jebat-core (2 stars, last pushed 2d ago), with no licence file. It adds 15 tokens to every session and 234 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
admet-reasoning
Interpretable ADMET analysis with mechanistic reasoning. Maps liabilities to structural causes and biological pathways. Based on CoTox (Park 2025) and DrugR (Liu 2026).
vibelution-continuous-optimization-loop
Runs one evidence-driven Vibelution optimization iteration from the ROI backlog: pick one todo item, worktree isolate, implement, machine-verify, merge, update STATE. Use when the user starts /loop for project improvement, continuous optimization, or agent-dev ROI backlog work.
dspy-react-agent-builder
Use for ReAct agents, tool-calling agents, dspy.ReAct, multi-step reasoning and acting, and GEPA agent optimization.
Jupyter Live Kernel
Guides notebook-first analysis with reproducible kernels, inspectable data loading, and explicit promotion paths back into durable code.
deep-reasoning
Structured multi-step reasoning tool for complex problem solving with branching, hypothesis testing, and evidence tracking.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…