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 cortex-tms/cortex-tms --skill syncgit clone --depth 1 https://github.com/cortex-tms/cortex-tmsWrote 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/cortex-tms/cortex-tms/sync)<a href="https://agentmods.dev/skills/cortex-tms/cortex-tms/sync"><img src="https://agentmods.dev/badge/skills/cortex-tms/cortex-tms/sync/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/cortex-tms/cortex-tms/sync"><img src="https://agentmods.dev/badge/skills/cortex-tms/cortex-tms/sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 20 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.00040 | $0.00311 |
| Opus 5.5 | $0.00016 | $0.00124 |
| Sonnet 5.5 | $0.00008 | $0.00062 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
sync 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.
What it actually says
Sync
Synchronize Cortex TMS task files and documentation.
Steps
- Read current state — check NEXT-TASKS.md, FUTURE-ENHANCEMENTS.md, README.md, CHANGELOG.md, package.json
- Update NEXT-TASKS.md — mark completed items, remove stale tasks, add new items if discussed
- Update FUTURE-ENHANCEMENTS.md — sync status markers (Planned/In Progress/Complete)
- Truth-sync source-of-truth files — ensure README, CHANGELOG reflect what actually shipped
- Archive if needed — move completed sprint content to docs/archive/
- Run validation —
node bin/cortex-tms.js validate --strictto confirm health - Show changes — run git diff and present for approval. Do not commit without approval.
Rules
- Do not modify src/, bin/, templates/, or any code files
- Follow the Propose/Justify/Recommend framework for any non-obvious changes
- If unsure whether something should be archived or updated, ask the user
Arguments
$ARGUMENTS
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 · 31 lines · 40 tokens per session scan A 7d4ddd21935f
sync is a skill published in the GitHub repository cortex-tms/cortex-tms (180 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 311 once invoked, about $0.0002 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
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
atlas-present
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
yds-gh-issue-drafter
Turn a rough, hand-written intent into a well-scoped GitHub Issue before planning starts. Takes a loose 'what I want' from the user, proposes the missing structure (Done definition, Out of scope, Design constraints), gets the user's approval, and creates the Issue via the gh CLI with a scoped-issue marker so…
yds-report-to-issues
Parses reports generated by the yds-software-evaluation or yds-vulnerability-scan skills and interactively registers selected tasks as GitHub Issues using the gh CLI. Use when the user wants to convert an evaluation report (docs/evaluation/.md) or security audit report (docs/security-audit/.md) into GitHub Issues.…