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.
git clone --depth 1 https://github.com/miyatti777/ai-plcWrote 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/rules/miyatti777/ai-plc/ai-plc-adaptive)<a href="https://agentmods.dev/rules/miyatti777/ai-plc/ai-plc-adaptive"><img src="https://agentmods.dev/badge/rules/miyatti777/ai-plc/ai-plc-adaptive/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/rules/miyatti777/ai-plc/ai-plc-adaptive"><img src="https://agentmods.dev/badge/rules/miyatti777/ai-plc/ai-plc-adaptive.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.00591 | $0.00591 |
| Opus 5.5 | $0.00236 | $0.00236 |
| Sonnet 5.5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
ai-plc-adaptive 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 28d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-PLC Adaptive Workflow
When to Use (RUL_plc_adaptive §0)
"Record broadly, keep procedures lean": decide separately whether a Layer (record) is needed and which safeguards apply. One-off / generic / personal work gets no Layer; work you will revisit or that spans sessions gets a Layer with ○/× done criteria; work needing repository- or org-specific context gets Context collection; decision material for others gets an independent review per task; irreversible actions by the AI (publish, send, core rules/skills, external DB, delete, money) need human approval first. If the depth suggested here differs from the criteria below, the criteria win and the reason goes in workflow_depth_reason.
Workflow Depth Detection
| Depth | Criteria | Pipeline Behavior | Verification |
|---|---|---|---|
| Simple | Single domain, 1-2 tasks, known pattern | Stage 1→4 direct (Stage 3 only when the conditions below apply) | L1 only |
| Standard | Multiple tasks, no Sub-Layer needed | Stage 1→2→4 (Stage 3 only when the conditions below apply) | L1+L2 |
| Complex | Recursive decomposition needed, large scale | All 4 stages + Sub-Layer recursion | L1+L2+L3+NFR |
Mode Detection
| Mode | Condition | Pipeline |
|---|---|---|
| Direct | One-time execution | Stage 1-4, complete |
| Platform Builder | Building reusable system | Stage 1-4 + Production Skill generation |
Next Action Routing
| Current State | Next Action |
|---|---|
| Stage 1 complete | → Stage 2 (Inception) |
| Stage 2 complete | backlog construction.required: true → Stage 3 (Construction); false → Stage 4 (Operation) |
| Stage 3 complete | → Stage 4 (Operation) |
| Task complete (more remain) | → Next executable task |
| All tasks complete (Direct) | → Pipeline end |
| All tasks complete (Platform Builder) | → Production Skill generation |
Stage 3 (Construction) is skipped by default
Run Stage 3 (Agent definitions) only when: complex depth, platform_builder mode, construction_mode: always in intent.yaml, a task with delegable: true, or an implementation/coding task with more than 5 steps. Whoever writes the backlog records the decision in the top-level construction (required / reason / tasks). Without Stage 3, Operation executes from the backlog (description, acceptance_criteria, guardrails, decisions) and Context. See RUL_plc_adaptive §6.
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.
- 28d ago Changed · +8 lines · +297 tokens per session a113a45588a8
- 2mo ago First seen · 33 lines · 294 tokens per session scan A 98a84463d86d
ai-plc-adaptive is a cursor rule published in the GitHub repository miyatti777/ai-plc (49 stars, last pushed 7d ago), licensed MIT. It adds 591 tokens to every session, about $0.0024 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-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.