Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/KonghaYao/perinpx agentmods add skills/konghayao/peri/ultra-adlcWrote 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/konghayao/peri/ultra-adlc)<a href="https://agentmods.dev/skills/konghayao/peri/ultra-adlc"><img src="https://agentmods.dev/badge/skills/konghayao/peri/ultra-adlc/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/konghayao/peri/ultra-adlc"><img src="https://agentmods.dev/badge/skills/konghayao/peri/ultra-adlc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 58 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 407 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00069 | $0.13194 |
| Opus 5 | $0.00034 | $0.06597 |
| Sonnet 5 | $0.00014 | $0.02639 |
| Haiku 4.5 | $0.00007 | $0.01319 |
Grade A, and why
ultra-adlc 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 — 1,285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ultra-ADLC
Turn one natural-language goal into a complete, audited delivery. The Main Agent
preserves the user's stated intent and authority boundaries, delegates ordinary
design adjudication to an independent opus or fable arbiter, and coordinates
all execution without making the user supervise implementation choices.
This skill is self-contained. Use the existing deferred Workflow tool and its
existing agent, parallel, pipeline, phase, and ordinary JavaScript control
flow only. Do not add a DAG/runtime/RPC/event/TUI primitive or a third logical
workflow.
Admission and completion invariants
- This mode is for a very large end-to-end task. If it was selected implicitly
for ordinary work, do the work normally instead. An explicit
/ultra-adlcinvocation always selects this mode. - There are exactly two logical workflows:
discovery-designanddelivery-convergence. A resumed physical run remains part of its original logical workflow. - The Main Agent is the only user-interaction seam. Workflow Agents cannot and
must not call
AskUserQuestion. User adjudication is not the default: ordinary reversible product, scope, risk, and design choices go to an independentopusorfableDecision Arbiter. Ask the user only for missing product intent, new authority, secret or external state, legally or financially consequential acceptance, irreversible action, or two outcomes that materially affect the user and cannot be resolved from the stated goal. - There are exactly three contracts:
intent.md,execution.md, andevidence.md. Manifests, decisions, handoffs, artifacts, and learning records are audit records, not extra contracts. - Legal terminal states are
complete,blocked, andcancelled. There is nopartially_complete. "Core complete", "mostly complete", an exhausted context, or a normally exited Workflow are never completion evidence. - Assessor verdicts are only
complete | incomplete | blocked. Do not invent a fourth verdict such ascomplete_with_known_gaps. Every required check in the accepted Verification Plan must have current, attributable evidence. Unrun or missing required tests, missing required coverage evidence, and unevidenced acceptance scenarios are coverage gaps: returnincompletewhen fixable inside Workflow 2, orblockedwhen an external dependency or authorization prevents obtaining the evidence. Keep fixable incomplete items inside the Workflow 2 loop.Remaining Risksmay contain only non-required checks outside the accepted Verification Plan (including an out-of-plan E2E or preexisting flake); it cannot excuse missing required evidence or reduce any completion percentage. - A task is
completeonly after one independent Completion Assessor in the current assessment round proves 100% coverage. Fixable gaps remain inside logical Workflow 2 and loop until they are fixed and reassessed. - Never commit, push, publish, deploy, delete material data, or mutate an external system unless the user separately and explicitly authorizes that action.
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 Changed · +696 lines 51023a73cd02
- 5d ago Changed · +130 lines ea83b0c03560
- 6d ago First seen · 459 lines · 69 tokens per session scan A 13c7f5f741a7
ultra-adlc is a skill published in the GitHub repository KonghaYao/peri (163 stars, last pushed today), licensed Apache-2.0. It adds 69 tokens to every session and 13,194 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
qa-testing
Verify your work by actually operating the app or website you changed, instead of assuming it works. Strongly recommended whenever you build, modify, or debug a web app, website, or desktop GUI app. Drive real browsers with the agent-browser CLI and native desktop apps with the cua-driver CLI. These are installed on…
remote-tests
Testing against remote executors in integration tests.
code-review-testing
For agent changes prefer integration tests over unit tests. Integration tests are under core/suite and use testcodex to set up a test instance of codex.
test-tui
Guide for testing Codex TUI interactively.
test-driven-development
A test-driven development guide. Test-driven development, or TDD, means writing a test first, confirming that it fails, then writing the smallest code that makes it pass and improving the result.
python-testing-patterns
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.