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 rules/instructa/viber3d/004-actionsgit clone --depth 1 https://github.com/instructa/viber3dWhat 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.00591 |
| Opus 5 | $0.00000 | $0.00296 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
004-actions 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 yesterday.
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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Actions Guidelines
Purpose
- Actions are centralized functions that modify the ECS world in predictable ways.
- They keep spawn/remove/update logic out of components and systems, providing a single place for entity manipulation.
Core Principles
- Single Entry Points
Write all creation, destruction, or major trait updates in these functions. - Pure ECS Focus
Do not add external side effects or UI manipulation. - Descriptive Names
Use clear names likespawnEnemy(),applyDamage(), ordestroyEntity().
Recommended Usage
import { createActions } from 'koota'
import { IsEnemy, Transform, Health } from '../traits'
export const actions = createActions((world) => ({
spawnEnemy: (position) => {
return world.spawn(
IsEnemy(),
Transform({ position }),
Health({ amount: 50 })
)
},
damageEntity: (entity, amount) => {
if (entity.has(Health)) {
entity.set(Health, (h) => {
const newAmount = Math.max(0, h.amount - amount)
if (newAmount <= 0) {
actions.destroyEntity(entity)
}
return { ...h, amount: newAmount }
})
}
},
destroyEntity: (entity) => {
entity.destroy()
}
}))
Integration with React
- Use
useActions(actionsFile)fromkoota/reactto bind actions to the currentworld. - Keep React components free of direct ECS manipulation. Call these action functions instead.
function GameInit() {
const { spawnEnemy } = useActions(actions)
useEffect(() => {
spawnEnemy({ x: 0, y: 5, z: 0 })
}, [])
return null
}
Testing Actions
- Create a fresh
worldin each test and bind actions withactions.bindTo(world). - Verify entity changes after calling each action.
describe('actions', () => {
let world
let boundActions
beforeEach(() => {
world = createWorld()
boundActions = actions.bindTo(world)
})
it('spawnEnemy creates an enemy entity', () => {
const ent = boundActions.spawnEnemy({ x: 0, y: 1, z: 0 })
expect(ent.has(IsEnemy)).toBe(true)
})
})
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.
- yesterday First seen · 97 lines · 0 tokens per session scan A 560f101cf6fc
004-actions is a cursor rule published in the GitHub repository instructa/viber3d (623 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 591 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 cursor rules, from other repositories
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
cypress-e2e-testing-cursorrules-prompt-file
Cursor rules for Cypress development with E2E testing.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
node-dependencies
Enforce Node.js versioning and package management best practices.
security-standards
Cursor rule "security-standards" from wjgogogo/cursor-rules, covering 安全规范, 核心原则 [p0], 输入验证, xss 防护 and csrf 防护.