agentmods.dev

PowerScroll: Instructions file for Codex

AGENTS.md

PowerScroll AGENTS.md is an instructions file for Codex, OpenCode from CynaCons/PowerScroll. It costs 468 tokens per session, scanned A, original, MIT.

A project instruction guide for PowerScroll. It defines the required tests, requirement records, canvas-testing methods, and checks to run before reporting completion.

In plain words
What is it for?
Use it when changing PowerScroll to find the right test locations, link behavior to requirements, and run type checks, linting, and browser tests.
Why use it?
It keeps coding work consistent and prevents agents from skipping required verification or using unreliable test techniques.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Codex.

This is CynaCons/PowerScroll's own configuration. It tells Codex and OpenCode how to work on PowerScroll itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PowerScroll configures →

not rated 0repo changed 23d ago A scan 468 tokens original MIT
View source ↗ CynaCons/PowerScroll cynacons.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to CynaCons/PowerScroll. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/CynaCons/PowerScroll/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/CynaCons/PowerScroll

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for PowerScroll AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cynacons/powerscroll/agents-md/github.svg)](https://agentmods.dev/instructions/cynacons/powerscroll/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/cynacons/powerscroll/agents-md"><img src="https://agentmods.dev/badge/instructions/cynacons/powerscroll/agents-md/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.

agentmods 80×15 button for PowerScroll AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cynacons/powerscroll/agents-md"><img src="https://agentmods.dev/badge/instructions/cynacons/powerscroll/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 468 This file is loaded in full into every session.
When invoked 468 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00468 $0.00468
Opus 5.5 $0.00187 $0.00187
Sonnet 5.5 $0.00094 $0.00094
Haiku 4.5 $0.00047 $0.00047

Measured 23d ago against content hash ec710aff673f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

PowerScroll AGENTS.md 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 23d 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.

AGENTS.md · 30 lines

What it actually says

Agent instructions (Codex, Grok, Gemini and other CLI agents)

Read CLAUDE.md first — it is the canonical project guide (stack, patterns, testing rules, showcase rules). The rules below are the ones sub-agents most often get wrong.

  • Tests: Playwright E2E only, in tests/<feature>/NN-name.spec.ts. Test numbers are globally unique across the whole project (check the highest existing number before adding one). Each spec header says Covers: REQ-XXX-NNN.

  • Requirements: every user-visible behaviour has a REQ-<AREA>-NNN row in docs/SRS_<AREA>.md with the covering test in the last column.

  • Verification before you report: npm run typecheck, npm run lint, then npx playwright test (full suite, ~3–5 min, starts its own Vite on port 5193, or $PW_PORT when the coordinator assigns you another one). Never enable retries. Report exact pass/fail counts.

  • Driving the canvas in tests: synthetic mouse events do not reach Konva. Use pointer events dispatched on the stage container, or set state through window.__POWERNOTE_STORES__ / window.__POWERNOTE_BRIDGE__. Look at tests/helpers.ts and an existing spec in the same folder first.

  • Do not commit, tag, bump versions, or edit PLAN.md unless your task explicitly says so. The coordinator owns those.

  • Style: simplicity over completeness. Small, readable diffs. No new dependencies unless the task names them.

  • Finish with a short summary: files changed, decisions taken, exact test numbers, anything left undone.

  • Never await import('/src/...') inside page.evaluate. Chromium can garbage-collect the evaluate's promise while the import is pending (CDP "Promise was collected", reported as "Execution context was destroyed"). Use preloadModule(page, path) from tests/helpers.ts before the evaluate and read (window as any).__mods[path] inside it.

Changes

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.

  1. 23d ago Changed · +5 lines · +94 tokens per session ec710aff673f
  2. 2mo ago First seen · 25 lines · 374 tokens per session scan A 7923f6e90172

Subscribe to this mod's changes

PowerScroll AGENTS.md is an instructions file published in the GitHub repository CynaCons/PowerScroll (0 stars, last pushed 2d ago), licensed MIT. It adds 468 tokens to every session, about $0.0019 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-09-04.

E2E testingReactTestingai-agentsinfinite-canvaslocal-firstmcpoffline-first
Related

PowerScroll AGENTS.md compared with instructions from other repositories

PowerScroll AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
PowerScroll AGENTS.mdCynaCons/PowerScrollInstructions file02d agoMITA468Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode