Borrowing it
Nothing to install: this file belongs to sepivip/SeekerClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sepivip/SeekerClaw/main/CLAUDE.mdgit clone --depth 1 https://github.com/sepivip/SeekerClawWrote 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/instructions/sepivip/seekerclaw/claude-md)<a href="https://agentmods.dev/instructions/sepivip/seekerclaw/claude-md"><img src="https://agentmods.dev/badge/instructions/sepivip/seekerclaw/claude-md.svg" alt="Measured on agentmods" 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.12001 | $0.12001 |
| Opus 5 | $0.06000 | $0.06000 |
| Sonnet 5 | $0.02400 | $0.02400 |
| Haiku 4.5 | $0.01200 | $0.01200 |
Grade A, and why
SeekerClaw CLAUDE.md scanned grade A with 1 finding 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 4d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `node`, `npm`, `npx` commands **cannot** be found or executed via `shell_exec` / `child_process` How it starts
The opening of the file, as written. The whole thing — 962 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — SeekerClaw Project Guide
Background research: See
docs/internal/RESEARCH.md| Source of truth: SeePROJECT.md
PROJECT.md — Source of Truth
- Read
PROJECT.mdbefore any feature work - After shipping any feature: update Shipped section + Changelog
- After starting any feature: move it to In Progress
- Keep Limitations section honest — if it doesn't work, list it
- One-Liner and Elevator Pitch should always reflect current state
- Update Stats periodically (tool count, skill count, lines of code)
Design Principle: UX First
Always think about user experience. This is the top priority when building SeekerClaw. Every UI decision, feature implementation, and config flow should be designed from the user's perspective. Ask: "Is this intuitive? Will the user lose data? Is switching between options seamless?" When in doubt, prioritize ease of use over technical elegance.
What Is This Project
SeekerClaw (package: com.seekerclaw.app) is an Android app that turns a Solana Seeker phone into a 24/7 personal AI agent. It embeds a Node.js runtime via nodejs-mobile and runs the OpenClaw gateway as a foreground service. Users interact with their agent through Telegram — the app itself is minimal (setup, status, logs, settings).
Supported Devices
- Primary: Solana Seeker (Android 14, Snapdragon 6 Gen 1, 8GB RAM)
- Secondary: Any Android 14+ with 4GB+ RAM
- Note: OEM-modified ROMs (Xiaomi MIUI, Samsung OneUI) may aggressively kill background services — Seeker's stock Android avoids this.
Development Phases
- Phase 1 (PoC): Mock OpenClaw with a simple Node.js Telegram bot (
grammy/telegraf) that responds to a hardcoded message. Proves Node.js runs on device, Telegram round-trip works. - Phase 2 (App Shell): Replace mock with real OpenClaw gateway bundle. Full setup flow, all screens, watchdog, boot receiver.
Version Tracking (KEEP UPDATED)
When updating OpenClaw or nodejs-mobile, update these version strings in ONE place:
app/build.gradle.kts→ theopenclawVersion/nodejsVersionvals at the top of the file.The app version (
versionName/versionCode) is also inapp/build.gradle.kts, asappVersionName/appVersionCode. All four are declared once and referenced from everywhere else — never retype a value a second time, or the copies drift.Identity is read at RUNTIME — never off
BuildConfig(BAT-1293). UI and diagnostics getversionName/versionCodefromBuildProvenance.installed(context), which asksPackageManagerabout the installed package, andcommit/dirty/openclawVersion/nodejsVersionfromBuildProvenance.get(context), which reads the packagedassets/build-metadata.json(app/src/main/java/com/seekerclaw/app/config/BuildProvenance.kt).A
buildConfigFieldfor any identity value is FORBIDDEN: it compiles to astatic final, which is INLINED into every reader, so when the value changes incremental compilation does not recompile those readers and they keep the OLD literal — that is how a build reported a SHA it did not contain. Andbuild-metadata.jsonis a build-time COPY, so it is the source for the engine and commit fields only, never forversionName/versionCode.tests/nodejs-project/build-identity-invariant.test.jsenforces both halves in CI.
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.
- 4d ago Changed · +20 lines · +343 tokens per session cfd80aa54506
- 8d ago First seen · 942 lines · 11,658 tokens per session scan A b470cc40963a
SeekerClaw CLAUDE.md is an instructions file published in the GitHub repository sepivip/SeekerClaw (314 stars, last pushed today), licensed MIT. It adds 12,001 tokens to every session, about $0.0600 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.