openclaw-100k-posts-kit AGENTS.md

Repository instructions for a content-production toolkit called 100k-posts-kit. They define how its agents, workspace files, demo voice, production voice, and local scripts should be used.

In plain words
What is it for?
Use them when running or changing the Virlo-to-content workflow, including content analysis, pattern reports, content creation, and the Monday publishing process.
Why use it?
They keep shared workspace behaviour consistent and make clear which voice profile and automation mode applies. This avoids mixing demo content with production content.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/themattberman/openclaw-100k-posts-kit/agents-md
Clone the repo
git clone --depth 1 https://github.com/TheMattBerman/openclaw-100k-posts-kit

Made for: Codex, OpenCode.

Per session 328 This file is loaded in full into every session.
When invoked 328 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00328 $0.00328
Opus 5 $0.00164 $0.00164
Sonnet 5 $0.00066 $0.00066
Haiku 4.5 $0.00033 $0.00033

Measured 3d ago against content hash f90027df459e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openclaw-100k-posts-kit 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 3d 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 · 42 lines

What it actually says

AGENTS

This repo is packaged as 100k-posts-kit.

Purpose

Use this package to demo or run an OpenClaw-native content pipeline:

Virlo -> Content DNA Batch -> Pattern Report -> The Forge -> Monday Drop

Optional research layer:

Content Radar adds Reddit and X discussion signal when available.

Default Agent Rules

  • Read docs/workspace-contract.md before changing shared workspace behavior.
  • Treat ~/clawd/workspace/brand/voice-profile.md as the source of truth for production voice.
  • Treat skills/the-forge/demo-voice-profile.md as demo-only fallback behavior.
  • Prefer the local shell scripts over ad hoc manual steps when demonstrating the workflow.
  • Be explicit about what is fully automated versus agent-assisted.

Voice Handling

  • Production mode: use /voice-lab to build the user's real voice profile.
  • Demo mode: if the user wants a fast example, run with Yames first.
  • Do not present Yames as the intended long-term voice.

Core Paths

  • skills/ contains the OpenClaw skill definitions.
  • scripts/monday-drop.sh is the main local orchestration entrypoint.
  • docs/workspace-contract.md defines cross-skill file ownership and output locations.
  • DEMO-GUIDE.md is the operator-facing walkthrough.
  • SETUP.md is the public install and configuration guide.

Release Posture

  • Keep public docs free of private-project references.
  • Keep required dependencies honest.
  • Preserve the demo path, but label it clearly as demo behavior.
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. 3d ago First seen · 42 lines · 328 tokens per session scan A f90027df459e

Subscribe to this mod's changes

openclaw-100k-posts-kit AGENTS.md is an instructions file published in the GitHub repository TheMattBerman/openclaw-100k-posts-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 328 tokens to every session, about $0.0016 per session on Opus 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.

Related

Other instructions, from other repositories

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens