Borrowing it
Nothing to install: this file belongs to zhuangguangdahyh-dotcom/content-ops-studio. 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/zhuangguangdahyh-dotcom/content-ops-studio/main/AGENTS.mdgit clone --depth 1 https://github.com/zhuangguangdahyh-dotcom/content-ops-studioWrote 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/zhuangguangdahyh-dotcom/content-ops-studio/agents-md)<a href="https://agentmods.dev/instructions/zhuangguangdahyh-dotcom/content-ops-studio/agents-md"><img src="https://agentmods.dev/badge/instructions/zhuangguangdahyh-dotcom/content-ops-studio/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.
<a href="https://agentmods.dev/instructions/zhuangguangdahyh-dotcom/content-ops-studio/agents-md"><img src="https://agentmods.dev/badge/instructions/zhuangguangdahyh-dotcom/content-ops-studio/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00591 | $0.00591 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
content-ops-studio 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Ops Studio repository instructions
Repository purpose
This repository develops content-ops-studio, a multi-industry image-post content production Plugin. Version 0.1.0 is a contract and engineering bootstrap with a gated Feishu China Workspace Adapter; live readiness requires explicit sandbox evidence. It does not provide production research, image-generation, rendering, publishing, MCP, or attachment-upload behavior.
Use the terms Operator (the person operating the Plugin), Subject (the person, brand, organization, store, or product represented), and Audience (the people the content is intended to influence). Do not collapse these roles into the ambiguous word "user".
Source hierarchy
- Current mandatory official OpenAI technical requirements.
- Accepted ADRs under
docs/decisions/. - This
AGENTS.md. - Directory-scoped
AGENTS.mdfiles. - The concrete task request.
A concrete task may change implementation details, but it may not bypass safety, data protection, factual accuracy, tool permissions, or the accepted state machine.
Core engineering rules
- Read the relevant documents and accepted ADRs before changing core behavior.
- Never commit real customer data, Feishu credentials, API keys, access tokens, private images, real chat logs, or non-anonymized business material.
- Every future external write must have a
run_id, idempotency key, pre-write state check, post-write read verification, and traceable error report. - Validate every state change against the state machine.
- Every Schema change requires migration notes and a migration test.
- Never overwrite approved content.
- Never implement failure rollback by deleting history.
- Explain the necessity of any new production dependency before adding it.
- Test deterministic core logic.
- Keep all examples fictional, anonymized, or sanitized.
- Never write project runtime data into the Plugin installation directory.
- Never treat chat memory as a project data source.
- Never fabricate tool success, external writes, or image-generation results.
- Never automatically modify a core Skill, platform pack, or industry pack.
- Version 0.1.0 supports only Node.js 24 LTS (
>=24 <25); Runtime support must never be conflated with production integration readiness.
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.
- 9d ago First seen · 58 lines · 591 tokens per session scan A 25ed6e96b82a
content-ops-studio AGENTS.md is an instructions file published in the GitHub repository zhuangguangdahyh-dotcom/content-ops-studio (0 stars, last pushed 13d ago), licensed MIT. It adds 591 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
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.
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).
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.
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).
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.