positioning-plugin AGENTS.md

Repository instructions for a positioning plugin whose main feature is a positioning skill. They explain where the skill lives, how to invoke it, how to keep it portable across coding-agent tools, and which version files must stay in sync.

In plain words
What is it for?
They are for developing, invoking, and maintaining the positioning skill and its plugin metadata.
Why use it?
They prevent changes that would make the skill undiscoverable, tied to one agent, or inconsistent across its version metadata.

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/gerstep/positioning-plugin/agents-md
Clone the repo
git clone --depth 1 https://github.com/Gerstep/positioning-plugin

Made for: Codex, OpenCode.

Per session 260 This file is loaded in full into every session.
When invoked 260 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.00260 $0.00260
Opus 5 $0.00130 $0.00130
Sonnet 5 $0.00052 $0.00052
Haiku 4.5 $0.00026 $0.00026

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

Security

Grade A, and why

positioning-plugin 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 2d 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 · 24 lines

What it actually says

positioning-plugin

This repo ships one Agent Skill: skills/positioning/. It is also discoverable at .agents/skills/ (a symlink) so Codex finds it when working inside this repo.

To use the skill here: /positioning in Claude Code or Cowork, $positioning in Codex.

To work on the skill:

  • The entry point is skills/positioning/SKILL.md. Keep it lean; details belong in references/ (progressive disclosure), output templates in assets/.
  • SKILL.md frontmatter must stay within the Agent Skills spec fields (name, description, license, compatibility, metadata, allowed-tools) so the skill stays portable across Claude Code, Cowork, Codex, and claude.ai uploads. metadata values must be strings.
  • Do not hard-depend on any harness-specific tool. Interactive question tools, subagents, and web search are all optional with plain-text fallbacks spelled out in SKILL.md.
  • Bump version in .claude-plugin/plugin.json, marketplace.json, and the SKILL.md metadata together.
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. 2d ago First seen · 24 lines · 260 tokens per session scan A 37c05858b57d

Subscribe to this mod's changes

positioning-plugin AGENTS.md is an instructions file published in the GitHub repository Gerstep/positioning-plugin (108 stars, last pushed 26d ago), licensed MIT. It adds 260 tokens to every session, about $0.0013 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

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

buildNext

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

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

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

spec-kit 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,040 tokens

langchain 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