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/kangarooking/tiktok-gen/agents-mdgit clone --depth 1 https://github.com/kangarooking/tiktok-genWrote 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/kangarooking/tiktok-gen/agents-md)<a href="https://agentmods.dev/instructions/kangarooking/tiktok-gen/agents-md"><img src="https://agentmods.dev/badge/instructions/kangarooking/tiktok-gen/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.1 | $0.00650 | $0.00650 |
| Opus 5 | $0.00325 | $0.00325 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
tiktok-gen 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 — 46 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 has a split architecture:
frontend/: React + TypeScript (Vite). Main UI code is inpages/, shared UI incomponents/, API calls inservices/, and app bootstrap inApp.tsxandindex.tsx.backend/: FastAPI service. API routes live inapp/api/v1/, business logic inapp/services/, integrations inapp/integrations/, data models inapp/models/, and schemas inapp/schemas/.docs/: product, API, and database documentation (schema.sql, interface docs).
Keep generated artifacts (frontend/dist/, node_modules/, __pycache__/) out of code reviews unless explicitly relevant.
Build, Test, and Development Commands
Frontend (frontend/):
npm install: install dependencies.npm run dev: start local Vite dev server.npm run build: produce production build infrontend/dist/.npm run preview: preview the production bundle.
Backend (backend/):
pip install -r requirements.txt: install Python dependencies.python init_db.py: initialize database tables.uvicorn app.main:app --reload --host 0.0.0.0 --port 3001: run API locally.celery -A app.tasks worker --loglevel=info --pool=solo: run async worker.
Coding Style & Naming Conventions
- Python: PEP 8, 4-space indentation,
snake_casefor functions/modules,PascalCasefor classes. - TypeScript/React: 2-space indentation,
PascalCasefor components (AssetsStudio.tsx),camelCasefor variables/functions. - Keep route files resource-oriented (
assets.py,projects.py) and services action-oriented (generation_service.py).
Testing Guidelines
- Backend test stack is
pytest+pytest-asyncio. - Place tests under
backend/tests/usingtest_*.pynaming. - Run tests with:
pytest backend/tests -v. - Add at least one API-level test for new endpoints and one service-level test for non-trivial logic.
Commit & Pull Request Guidelines
Git history is not available in this exported directory, so follow this standard:
- Commit format:
type(scope): short description(example:feat(api): add avatar upload validation). - Use focused commits; avoid mixing frontend/backend refactors with feature changes.
- PRs should include: summary, changed paths, verification steps, linked issue, and screenshots for UI changes.
- Call out config changes (
.env.example, API keys, ports) explicitly in the PR description.
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 · 46 lines · 650 tokens per session scan A b49ae1ee0302
tiktok-gen AGENTS.md is an instructions file published in the GitHub repository kangarooking/tiktok-gen (88 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 650 tokens to every session, about $0.0032 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
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 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.
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.
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.
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).