agentmods.dev

marketplace: Instructions file for Claude Code

AGENTS.md

marketplace AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from BitYoungjae/marketplace. It costs 588 tokens per session, scanned A, original, MIT.

A set of contribution rules for a software repository, covering its folders, commands, coding style, and testing expectations.

In plain words
What is it for?
Use it when adding or installing plugins, syncing documentation, choosing file locations, following naming rules, or preparing tests and pull requests.
Why use it?
It gives developers a shared reference for making changes that fit the repository and for checking them consistently.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: Claude Code plugin machinery, but also the file is AGENTS.md. Also seen: mentions Claude Code.

This is BitYoungjae/marketplace's own configuration. It tells Claude Code, Codex and OpenCode how to work on marketplace itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything marketplace configures →

not rated 6repo 3mo ago A scan 588 tokens original MIT
View source ↗ BitYoungjae/marketplace
Reuse

Borrowing it

Nothing to install: this file belongs to BitYoungjae/marketplace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/BitYoungjae/marketplace/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/BitYoungjae/marketplace

Made for: Claude Code, Codex, OpenCode.

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

agentmods badge for marketplace AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bityoungjae/marketplace/agents-md.svg)](https://agentmods.dev/instructions/bityoungjae/marketplace/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/bityoungjae/marketplace/agents-md"><img src="https://agentmods.dev/badge/instructions/bityoungjae/marketplace/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 588 This file is loaded in full into every session.
When invoked 588 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00588 $0.00588
Opus 5 $0.00294 $0.00294
Sonnet 5 $0.00118 $0.00118
Haiku 4.5 $0.00059 $0.00059

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

Security

Grade A, and why

marketplace 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 8d 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 · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

  • plugins/ contains publishable Claude Code plugins (dokhak, gitkkal, nvim-doctor, obsidian-blocks, omarchy).
  • Each plugin keeps metadata in .claude-plugin/plugin.json, plus capability folders such as commands/, skills/, agents/, and optional contexts/.
  • contexts/ stores shared reference documents (for example contexts/cc/ synced Claude Code docs).
  • scripts/ contains maintenance utilities (currently scripts/cc-docs-sync.sh).
  • .github/PULL_REQUEST_TEMPLATE.md defines PR expectations.

Build, Test, and Development Commands

  • No compile/build step is required; this repository is Markdown/JSON-first.
  • Add marketplace and install a plugin locally: 
    /plugin marketplace add bityoungjae/marketplace
/plugin install gitkkal@bityoungjae-marketplace
  • Sync Claude Code docs: 
    ./scripts/cc-docs-sync.sh --dry-run
./scripts/cc-docs-sync.sh --include-prompt-engineering --verbose
    Use --dry-run before writing files.

Coding Style & Naming Conventions

  • Use Markdown for docs and command/skill definitions; keep sections short and task-oriented.
  • Use 2-space indentation in JSON files (see plugins/*/.claude-plugin/plugin.json).
  • Use kebab-case for plugin and skill directories (for example plugins/obsidian-blocks/skills/mermaid-diagramming/).
  • Command files should map directly to slash commands (for example commands/diagnose.md -> /nvim-doctor:diagnose).
  • If English and Korean READMEs both exist, update both when behavior changes.

Testing Guidelines

  • There is no centralized automated test suite yet.
  • For each change, run focused manual validation:
    1. Verify referenced files in updated plugin.json exist.
    2. Exercise changed commands/skills in Claude Code.
    3. If docs sync changed, run ./scripts/cc-docs-sync.sh --dry-run to confirm target diffs.

Commit & Pull Request Guidelines

  • Preferred commit format follows Conventional Commits with optional scope:
    • feat(dokhak): add model-aware tool selection
    • docs(obsidian-blocks): update mermaid note
  • Emoji-style subjects appear in history, but keep messages clear, scoped, and actionable.
  • Open PRs using .github/PULL_REQUEST_TEMPLATE.md: complete Summary, Changes, Test Plan, and checklist items for style/docs updates.
  • Link related issues/PRs in the title or body (for example (#5)).

Read the full file on GitHub · 45 lines

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. 8d ago First seen · 45 lines · 588 tokens per session scan A e369ba21955b

Subscribe to this mod's changes

marketplace AGENTS.md is an instructions file published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 588 tokens to every session, about $0.0029 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.

Related

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.

vercel/next.js · 7,296 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,153 tokens

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

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

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,469 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