agentmods.dev

vardiya: Instructions file for Codex

AGENTS.md

vardiya AGENTS.md is an instructions file for Codex, OpenCode from Zulwatha/vardiya. It costs 677 tokens per session, scanned A, original, MIT.

Development instructions for Vardiya, a Node.js job queue that stores jobs in SQLite, a small database held in a file.

In plain words
What is it for?
Use them when changing Vardiya's storage, workers, scheduler, utilities, public API, tests, or benchmarks.
Why use it?
They divide the code into ownership areas and protect shared interfaces so multiple agents can work without conflicting changes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is Zulwatha/vardiya's own configuration. It tells Codex and OpenCode how to work on vardiya 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 vardiya configures →

not rated 10repo 3mo ago A scan 677 tokens original MIT
View source ↗ Zulwatha/vardiya npmjs.com
Reuse

Borrowing it

Nothing to install: this file belongs to Zulwatha/vardiya. 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/Zulwatha/vardiya/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Zulwatha/vardiya

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 vardiya AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/zulwatha/vardiya/agents-md"><img src="https://agentmods.dev/badge/instructions/zulwatha/vardiya/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 677 This file is loaded in full into every session.
When invoked 677 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.00677 $0.00677
Opus 5.5 $0.00271 $0.00271
Sonnet 5.5 $0.00135 $0.00135
Haiku 4.5 $0.00068 $0.00068

Measured 2mo ago against content hash 1c7f5dd7f254, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vardiya 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 2mo 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 · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent ownership map

vardiya is a SQLite-backed job queue for Node.js. One runtime dependency (better-sqlite3). This repo is split so several agents can work in parallel without stepping on each other.

Module owners

Area Path Owner Responsibility
Types / contract src/types.ts Lead (frozen) Shared interfaces and types. Do not edit.
Public API stubs src/index.ts, src/vardiya.ts Lead (signatures frozen) Export surface. Fill bodies only; do not change method signatures.
Utilities src/util/ Shared Small pure helpers (ids, sleep, typed emitter).
Storage src/storage/ Agent A SQLite schema, migrations, Storage implementation.
Worker src/worker/ Agent B Claim loop, handlers, concurrency, heartbeats, events.
Scheduler src/scheduler/ Agent C In-house cron parsing, repeatables, delayed promotion ticks.
Tests & benches test/, bench/ Agent D Vitest tests and benchmarks.

Stay inside your directory unless you need a tiny shared helper in src/util/. Prefer asking for a util over inventing a second copy.

Frozen types rule

src/types.ts is frozen after the foundation task. If you believe a change is required, do not edit the definitions. Add a comment block like this near the call site or in your PR notes:

/*
 * PROPOSED-CHANGE:
 * What: add Storage.reclaimStale(now, staleAfterMs)
 * Why: workers die mid-job and active rows need reclaim
 * Suggested shape: reclaimStale(now: number, staleAfterMs: number): number
 */

The lead merges contract changes deliberately so parallel work does not break.

Stack reminders

  • Node >= 22, TypeScript strict, dual ESM+CJS via tsup.
  • Runtime dependency: better-sqlite3 only. Cron, backoff, and ids are in-house.
  • Lint/format with biome. Tests with vitest.
  • npm run build, npm run lint, and npm test should stay green.

Writing style

Binding for every agent and every file: code comments, TSDoc, READMEs, docs, commit messages, and error messages.

Read the full file on GitHub · 54 lines

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. 2mo ago First seen · 54 lines · 677 tokens per session scan A 1c7f5dd7f254

Subscribe to this mod's changes

vardiya AGENTS.md is an instructions file published in the GitHub repository Zulwatha/vardiya (10 stars, last pushed 3mo ago), licensed MIT. It adds 677 tokens to every session, about $0.0027 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.

background-jobsbetter-sqlite3cronjob-queuenodejsqueue
Related

vardiya AGENTS.md compared with instructions from other repositories

vardiya AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
vardiya AGENTS.mdZulwatha/vardiyaInstructions file103mo agoMITA677Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode