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/cortex-tms/cortex-tms/syncnpx skills add cortex-tms/cortex-tms --skill syncgit clone --depth 1 https://github.com/cortex-tms/cortex-tmsWhat 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.00040 | $0.00311 |
| Opus 5 | $0.00020 | $0.00156 |
| Sonnet 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 yesterday.
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.
- yesterday 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 8d ago), licensed MIT. It adds 40 tokens to every session and 311 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
design-decision-log
Use when a team needs to record significant technical decisions with context, rationale, and consequences for future reference.
cache_patterns
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
event_driven
Structure systems around asynchronous, event-based communication to decouple producers and consumers for improved scalability and resilience. Use when building loosely coupled systems with asynchronous message-based communication.
cache_patterns
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
event_driven
Structure systems around asynchronous, event-based communication to decouple producers and consumers for improved scalability and resilience. Use when building loosely coupled systems with asynchronous message-based communication.
init-workspace-documentation
Skill "init-workspace-documentation" from griddynamics/rosetta, covering agent memory.md, agent memory, preventive rules, what worked and what failed.