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/treex-x/workflowx/socratesxnpx skills add TreeX-X/WorkFlowX --skill socratesxgit clone --depth 1 https://github.com/TreeX-X/WorkFlowXWhat 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.00019 | $0.00681 |
| Opus 5 | $0.00010 | $0.00341 |
| Sonnet 5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
socratesX 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
socratesX
Use this skill as the xflow preflight, or when the user explicitly asks for Socratic clarification.
Purpose
Turn repository facts and user intent into a confirmed, executable brief for Hybrid Tree generation. Surface only assumptions, contradictions, boundaries, non-functional requirements, and implementation trade-offs that can change the work.
Responsibility boundary
module 08explores the repository and reports relevant facts, files, dependencies, and constraints.socratesXasks the user to resolve decisions that cannot be established from repository evidence.orchestrateXprojects the confirmed result into Parent/Child documents. It does not repeat requirement analysis.
Clarification protocol
- Work by analysis phase: goal and scope, behavior and boundaries, implementation direction, then verification and rollout.
- At the end of each phase, ask all unresolved questions found in that phase in one batch. Do not force one question per turn.
- Ask only questions whose answers can change scope, architecture, behavior, acceptance criteria, dependencies, or risk. Omit questions already answered by the request or repository evidence.
- Offer options only when there are two or more credible alternatives with a meaningful trade-off. For a fact, constraint, or single viable direction, ask directly. Do not manufacture options.
- Give a recommendation only when the evidence supports one. State the reason and the cost; allow the user to choose another direction.
- Do not invent missing intent. Mark unresolved items as
[Needs confirmation]and keep them out of the final scope until resolved. - Stop clarifying when the brief is sufficient to define Parent/Child scope and acceptance criteria. Do not keep asking low-impact preference questions.
Confirmation gate
Use an adaptive confirmation gate:
- If a phase has unresolved decisions, present the batched questions and wait for the user's answers.
- If the request is already sufficiently specified, skip exploratory questions and present one
Ready Summaryfor confirmation. - After the user confirms a decision, treat it as settled. Do not ask for confirmation again unless new evidence creates a material contradiction.
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.
- 2d ago First seen · 57 lines · 19 tokens per session scan A b399f34cc801
socratesX is a skill published in the GitHub repository TreeX-X/WorkFlowX (55 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 681 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-30.
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.
project-orchestration
Orchestrate multi-agent workflows for feature development using planning agents, context handoff, and stage management.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
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.
deep-researcher
Performs comprehensive, multi-layered research on any topic with structured analysis and synthesis of information from multiple sources.
llmtornado-tutorial-generator
Generates comprehensive code tutorials on LlmTornado API formatted for Medium publication with examples, explanations, and best practices.