Borrowing it
Nothing to install: this file belongs to TreeX-X/WorkFlowX. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TreeX-X/WorkFlowX/main/.claude/skills/noteX/SKILL.mdgit clone --depth 1 https://github.com/TreeX-X/WorkFlowXWrote 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/treex-x/workflowx/notex)<a href="https://agentmods.dev/skills/treex-x/workflowx/notex"><img src="https://agentmods.dev/badge/skills/treex-x/workflowx/notex/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/treex-x/workflowx/notex"><img src="https://agentmods.dev/badge/skills/treex-x/workflowx/notex.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00441 |
| Opus 5.5 | $0.00010 | $0.00176 |
| Sonnet 5.5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
noteX 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 7d 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
noteX
Search the relevant module entry and owning Notes before writing. Read originals through the shared wiki index; without it, use bounded rg and report unresolved references. Load only the current module, necessary parent context and explicit dependencies.
- Update an existing topic when it still owns the fact. Create a Note for independently useful content; create or merge a module directory only when responsibilities warrant it. Stay within the user's discussed change scope.
- Each module has one
module.mdentry with a complete overall explanation. Other Notes and submodules coexist beside it. Planned modules use the same structure with explicit status; unknowns remain unknown. - Use stable subject filenames, immutable UUIDs and full
note://repo-id/note-ididentity. Preservecreated; refresh UTCupdatedon every maintenance write, including moves and type conversions. Reads and no-op work do not touch time. - Keep current design in module documents, exploration in ideas, acceptance in requirements and durable trade-offs in decisions. Ideas may change type in place. Task ownership and creation follow the selected workflow.
- Reorganize or remove obsolete content when useful; repair live references and preserve required execution evidence. Read reorganization for moves, merges, deletion or legacy migration.
- Land affected code, relevant Note updates and necessary entry reverse references together. No Note change is needed when recorded facts remain correct. Write concise current facts; use proseX when drafting substantial narrative.
Read module structure when creating/changing module boundaries; wiki when resolving references, changing indexed sources or implementing a consumer. Load only the needed template from templates/; replace example UUIDs, ownership references and times. Keep metadata compact: two-space JSON with short nested values inline; preserve fields and exact values. The pinned harness-note/2 standard defines validation, not extra mandatory reading for ordinary edits.
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago Changed · -50 lines · -14 tokens per session de96682b0905
- 19d ago Changed · +15 lines cad04d596f51
- 27d ago Changed · -10 lines 057de32ac12a
- 1mo ago Changed · +1 lines ac342446186b
- 1mo ago First seen · 62 lines · 39 tokens per session scan A d6f4610ee855
noteX is a skill published in the GitHub repository TreeX-X/WorkFlowX (53 stars, last pushed 8d ago), licensed MIT. It adds 25 tokens to every session and 441 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-09-11.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.