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/opendcai/dataflow-loopai/analyzernpx skills add OpenDCAI/Dataflow-LoopAI --skill analyzergit clone --depth 1 https://github.com/OpenDCAI/Dataflow-LoopAIWhat 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.00000 | $0.01538 |
| Opus 5 | $0.00000 | $0.00769 |
| Sonnet 5 | $0.00000 | $0.00308 |
| Haiku 4.5 | $0.00000 | $0.00154 |
Grade A, and why
Analyzer 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzer Skill
Purpose
Analyzer Skill is the Codex/Agent-facing capability for running LoopAI Analyzer independently. It analyzes evaluation outputs, writes Analyzer reports, emits stream events, returns unified success/error payloads, and can compare current results with a historical baseline.
Python Implementation
The Python skill layer and Analyzer business implementation live in:
loopai/skills/Analyzer
Analyzer no longer depends on loopai/agents/Analyzer. The legacy agents-side
Analyzer directory has been removed; Codex and WebUI should call the skill
entry directly.
Runtime Entry
from loopai.skills.Analyzer import run, resume_run
run(state=None, resume=False, from_node=None, baseline_result_path=None)
resume_run(state=None, from_node=None, baseline_result_path=None)
run(...) is the Codex/sub-agent process entry. It emits the unified LoopAI
payload to stdout and exits, matching the latest Judger skill pattern. For
in-process calls use run_analyzer_standalone(...).
Use resume_run(...) for continuation. It always passes resume=True and
selects the latest incomplete version checkpoint for the task. A normal
run(...) also resumes the latest incomplete version by default. To explicitly
start a new run, pass new_version=True (or use the CLI --new-version).
{
"ok": true,
"status": "completed",
"message": "Analyzer completed.",
"data": {},
"error": null
}
Direct runner:
from loopai.skills.Analyzer.runner import run_analyzer_standalone
run_analyzer_standalone(...) keeps the legacy behavior and returns the final state directly.
LangGraph-compatible class import:
from loopai.skills.Analyzer.analyzer_agent import AnalyzerAgent
CLI
python examples/scripts/run_analyzer_standalone.py --config-path /tmp/analyzer_full_demo.json --baseline-result-path /tmp/analyzer_demo_baseline.jsonl --print-result
Supported options:
--config-path--resume--from-node--checkpoint-path--baseline-result-path--print-result--list-nodes--stream-stdout
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 · 214 lines · 0 tokens per session scan A de1462bc5daa
Analyzer is a skill published in the GitHub repository OpenDCAI/Dataflow-LoopAI (22 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,538 tokens. 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
loopx-auto-research
Use when a LoopX worker is operating an auto-research lane, demo pane, frontier item, evidence packet, promotion/retirement decision, or visible tmux/Codex auto-research rehearsal. Identity must come from the LoopX role profile and quota/frontier packet; this skill only provides role-specific execution checklists…
loopx-change-quality
Qualify the exact final diff for a LoopX-managed goal. Use when goal policy enables changequalityqualification, before a non-trivial delivery or merge, and when producing or repairing an exact-scope quality receipt. The workflow is language-neutral, permits at most one policy-authorized safe-fix pass, and never grants…
loopx-material
Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate/archive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off…
loopx-pr-review
Use for /loopx-pr-review or evidence-backed PR queue review. Run loopx pr-review first, execute the capability-owned review plan for each selected exact head, then publish full bilingual PR reviews (complete Chinese five-block review plus one concise English verdict) that match the verified findings. Use…
loopx-self-repair
Diagnose and repair LoopX control-plane drift or agent behavior drift. Use when a LoopX task makes unexpectedly small progress, follows a stale or contradictory recommendedaction, ignores a higher-priority blocked item while doing fallback work, reports vague owner/user gates, loses todo projection, misaligns…
loopx-pr-program
Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new/merged/closed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle/check/review changes over…