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/magnusnoeddegaard/tskills/agents-mdgit clone --depth 1 https://github.com/magnusnoeddegaard/tskillsWrote 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/magnusnoeddegaard/tskills/agents-md)<a href="https://agentmods.dev/instructions/magnusnoeddegaard/tskills/agents-md"><img src="https://agentmods.dev/badge/instructions/magnusnoeddegaard/tskills/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.01074 | $0.01074 |
| Opus 5 | $0.00537 | $0.00537 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
tskills 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 4d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working on this project.
Dev Environment
# Install dependencies
npm install
# Build TypeScript
npm run build
# Watch mode for development
npm run dev
# Link for local testing
npm link
After linking, test with:
tskills --help
ts --help
Project Structure
src/cli.ts- Entry point, registers all commands (local + registry + org/team)src/types.ts- TypeScript interfaces for skills, registry, orgs, teams, authsrc/commands/- Each file is a CLI command:- Registry:
login,logout,whoami,publish,install,uninstall,search,info,outdated,update,deprecate - Organizations/Teams:
org(subcommands: create, list, info, add, remove, delete),team(same subcommands) - Local/Legacy:
setup,init,add,import,list,sync,share,config
- Registry:
src/adapters/- Tool-specific output adapters (Claude, Cursor, Windsurf)src/lib/- Shared utilities:config.ts- Read/write~/.tskills/config.tomldiscover.ts- Auto-discover SKILL.md filesgit.ts- Clone/pull operationsskill.ts- Parse SKILL.md with YAML frontmattercredentials.ts- Auth token storage (~/.tskills/credentials.json)errors.ts- Custom error classes (Auth, Network, Validation, RateLimit, Permission, etc.)error-handler.ts- Maps Supabase/Postgres/FS errors to custom errorsmanifest.ts- Tracks installed skills (~/.tskills/installed.json)registry.ts- Supabase client + full registry API (~1000 lines)registry-config.ts- Dynamic registry config with remote fetch + cachingretry.ts- Retry with exponential backoff and jittervalidation.ts- Input validation (skill names, semver, slugs, usernames)
supabase/- Supabase project config and 14 SQL migrations
Backend (Supabase)
The registry backend is a Supabase project with:
- Postgres tables: users, skills, skill_versions, organizations, org_members, teams, team_members, rate_limits
- Row Level Security (RLS): visibility-based access control (public/private/org/team)
- RPC functions:
check_rate_limit,increment_downloads,create_org_with_owner - GitHub OAuth for authentication
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.
- 4d ago First seen · 139 lines · 1,074 tokens per session scan A 2b1bb63e7981
tskills AGENTS.md is an instructions file published in the GitHub repository magnusnoeddegaard/tskills (5 stars, last pushed 7mo ago), licensed MIT. It adds 1,074 tokens to every session, about $0.0054 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
mcp-unity AGENTS.md
Instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
rails-ai-context AGENTS.md
AGENTS.md instructions for crisnahine/rails-ai-context, covering rails-ai-context, agent skills, issue tracker, triage labels and domain docs.
inspecto CLAUDE.md
Instructions for inspecto-dev/inspecto, covering inspecto — claude code development guide, project overview, monorepo structure, development phases (load each file as needed) and key architectural decisions.
skill.color-expert CLAUDE.md
Claude Code instructions for meodai/skill.color-expert, covering claude.md, project overview, architecture, no build/test/lint and editing guidelines.
imagine-mcp AGENTS.md
AGENTS.md instructions for n24q02m/imagine-mcp, covering imagine-mcp, architecture, tool signatures, model selection and transport modes.
llm-ide-rules typescript.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering typescript and dates & times.