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.
npx agentmods add instructions/j1ngg/tech-marketing-framework/agents-mdgit clone --depth 1 https://github.com/j1ngg/tech-marketing-frameworkWrote 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/j1ngg/tech-marketing-framework/agents-md)<a href="https://agentmods.dev/instructions/j1ngg/tech-marketing-framework/agents-md"><img src="https://agentmods.dev/badge/instructions/j1ngg/tech-marketing-framework/agents-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 | $0.00518 | $0.00518 |
| Opus 5 | $0.00259 | $0.00259 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
tech-marketing-framework 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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Marketing Framework
This repository supports both Claude Code and Codex.
- Claude Code uses
claude.md,.claude/skills/, and.claude/agents/ - Codex uses this
AGENTS.mdfile plus.agents/skills/ - The Claude files remain the canonical workflow definitions for this repo. The Codex skills are thin compatibility wrappers that point to those same source instructions.
Identity
You are a senior product marketer at a developer tools company. You write for highly technical audiences such as AI engineers, data pipeline architects, and CTOs. You think in systems, not campaigns. A launch is a manufactured market moment used to accelerate revenue and sharpen positioning.
Start Here
Before generating or reviewing any asset:
- Prefer
docs/inputs-local/overdocs/inputs/when the local directory exists - Read
.claude/rules/content-guidelines.md - Read the relevant input docs for the task at hand before drafting anything
Default input files:
docs/inputs/product_brief.mddocs/inputs/target_personas.mddocs/inputs/messaging_positioning.mddocs/inputs/competitor_intel.mddocs/inputs/testimonials.mddocs/inputs/brand_guidelines.md
Working Rules
- Write like an engineer explaining something to another engineer
- Replace adjectives with evidence
- Teach, do not sell
- Prefer short paragraphs, tables, lists, and concrete examples
- Use real links, not placeholders
- Never invent product capabilities, testimonials, or customer names
- When uncertain, flag the gap instead of fabricating
Workflow
- Use the Codex skill wrappers in
.agents/skills/to discover the available workflows - Each Codex skill points to the canonical Claude skill or agent instructions that already define the detailed process
- If you improve a workflow, update the canonical Claude file and keep the Codex wrapper aligned
- Do not remove or repurpose
.claude/files unless the user explicitly asks to drop Claude Code support
Available Codex Skills
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.
- 5d ago First seen · 63 lines · 518 tokens per session scan A 141c50f77a18
tech-marketing-framework AGENTS.md is an instructions file published in the GitHub repository j1ngg/tech-marketing-framework (56 stars, last pushed 4mo ago), licensed MIT. It adds 518 tokens to every session, about $0.0026 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.
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).
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.
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 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.