agentic-awesome-skills AGENTS.md

Repository instructions stored in an AGENTS.md file. They explain how this project is organised, built, tested, and maintained.

In plain words
What is it for?
They are for working on this repository, including validating skills, running tests, rebuilding catalogue data, and developing its web app.
Why use it?
They give a coding agent the project’s local rules, reducing guesswork about commands, file locations, naming, and tests.

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/sickn33/agentic-awesome-skills/agents-md
Clone the repo
git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills

Made for: Codex, OpenCode.

Per session 1,425 This file is loaded in full into every session.
When invoked 1,425 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.01425 $0.01425
Opus 5 $0.00713 $0.00713
Sonnet 5 $0.00285 $0.00285
Haiku 4.5 $0.00143 $0.00143

Measured yesterday against content hash 53f1d5c10034, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentic-awesome-skills 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 55 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

This repository publishes an installable library of agent skills and plugin bundles. Canonical skill sources live in skills/<skill-id>/SKILL.md; use lowercase, hyphenated skill IDs. Mirrored plugin distributions live under plugins/. Contributor and user docs live in docs/; localized docs live in docs_zh-CN/ and docs/vietnamese/. Maintenance scripts and tests are in tools/scripts/ and tools/scripts/tests/. The hosted catalog app is in apps/web-app/. Registry outputs such as CATALOG.md, skills_index.json, and data/*.json are generated artifacts.

Build, Test, and Development Commands

  • npm ci: install root dependencies for scripts and validation.
  • npm run validate: validate skill frontmatter, required sections, and schema rules.
  • npm run security:docs: run safety checks for command, install, credential, and network guidance.
  • npm run test: run the repository script test suite.
  • npm run build: regenerate core indexes and build the catalog data.
  • npm run app:install: install apps/web-app dependencies.
  • npm run app:dev: start the local Vite catalog app.
  • npm run app:build: build and prerender the catalog app.

Before PRs, run npm run validate && npm run test && npm run security:docs.

Coding Style & Naming Conventions

Use Markdown for skills and docs, JavaScript/Node for most tooling, and Python for audits and sync helpers. Keep skill directories lowercase with hyphens, for example skills/my-awesome-skill/SKILL.md. Start new skills from docs/contributors/skill-template.md; include frontmatter, ## When to Use, examples, and limitations. Keep generated-file edits out of community PRs unless doing maintainer release or sync work.

Testing Guidelines

Tests live mainly in tools/scripts/tests/ and use Node assertions or Python unittest. Name new tests after the behavior under test, for example installer_filters.test.js or test_validate_skills_strict.py. Run targeted tests during development, then run the relevant npm scripts above. Web app changes should also run npm run app:test or npm run app:test:coverage.

Read the full file on GitHub · 55 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. yesterday First seen · 55 lines · 1,425 tokens per session scan A 53f1d5c10034

Subscribe to this mod's changes

agentic-awesome-skills AGENTS.md is an instructions file published in the GitHub repository sickn33/agentic-awesome-skills (45,746 stars, last pushed yesterday), licensed MIT. It adds 1,425 tokens to every session, about $0.0071 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.