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 OpenDCAI/Dataflow-LoopAI --skill analyzergit clone --depth 1 https://github.com/OpenDCAI/Dataflow-LoopAIWrote 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/opendcai/dataflow-loopai/analyzer)<a href="https://agentmods.dev/skills/opendcai/dataflow-loopai/analyzer"><img src="https://agentmods.dev/badge/skills/opendcai/dataflow-loopai/analyzer/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/opendcai/dataflow-loopai/analyzer"><img src="https://agentmods.dev/badge/skills/opendcai/dataflow-loopai/analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.04528 |
| Opus 5.5 | $0.00000 | $0.01811 |
| Sonnet 5.5 | $0.00000 | $0.00906 |
| Haiku 4.5 | $0.00000 | $0.00453 |
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 16d 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 — 449 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 compares completed versions of the same task and benchmark. Code, Text2SQL and Math Rollout share seven text reports, a training-plan JSON and a new annotated OJ copy.
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
What ships with it
4 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.
- 16d ago Changed · +170 lines e96ee281294d
- 1mo ago Changed · +65 lines dcec6eb23421
- 1mo ago First seen · 214 lines · 0 tokens per session scan A de1462bc5daa
Analyzer is a skill published in the GitHub repository OpenDCAI/Dataflow-LoopAI (29 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,528 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
b3os-verification
Skill "b3os-verification" from b3rys/b3rys-team-os, covering b3rys verification — prove it, and keep it proven, 1. three principles, 2. five ratchets — verification that only gets stronger, 3. layers and rubric and 4. proving the checks — mutants.
load-testing
Use when designing and executing load testing, stress testing, endurance testing, spike testing, and performance testing. Includes test planning, test script creation, result analysis, and performance optimization. Based on CPE certification and performance testing best practices.
test-automation-architecture
Use when designing test automation frameworks, implementing page object patterns, creating test reporting systems, and managing parallel test execution. Includes test strategy, test data management, and test infrastructure setup. Based on CTFL-TA and ISTQB Advanced Level certifications.
testing-strategy
Use when designing comprehensive testing strategies, implementing test coverage, setting up CI/CD quality gates, and defining unit, integration, and E2E test approaches. Includes testing pyramid, coverage thresholds, and test automation best practices. Based on software testing certification standards and industry…
tdd-workflow
Test-Driven Development workflow skill with patterns for unit, integration, and e2e testing. Use when implementing features to ensure all code is born tested with comprehensive coverage.
fix-failing-tests
Iteratively fix all failing tests until the test suite is green.