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/blackmichael/tuisky/agents-mdgit clone --depth 1 https://github.com/blackmichael/tuiskyWhat 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.01207 | $0.01207 |
| Opus 5 | $0.00603 | $0.00603 |
| Sonnet 5 | $0.00241 | $0.00241 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
tuisky 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file gives repo-specific guidance for coding agents working in this project.
Purpose
TuiSky is a terminal Bluesky client built with Bun + React + Gridland (a library built on top of OpenTUI). The codebase is small and UI-heavy. Most changes affect keyboard interaction, terminal layout, or optimistic state updates against the AT Protocol API.
Tech Stack
bunreact@gridland/bun@atproto/api
Core Commands
Install:
bun install
Run app:
bun run dev
Show CLI help or version without starting the TUI:
bun run dev -- --help
bun run dev -- --version
Build:
bun run build
Build with an explicit app version embedded at compile time:
bun run build -- --version 1.2.3
Build macOS release archives for GitHub Releases and Homebrew:
bun run build:release -- --version 1.2.3
Test:
bun test
Release Flow
- GitHub tag pushes matching
v*trigger.github/workflows/release.yml. - The workflow builds native
darwin-arm64anddarwin-x64archives, publishes them to the GitHub Release, and writeschecksums.txt. - After publishing assets, the workflow opens a PR against
blackmichael/homebrew-tapupdatingFormula/tuisky.rb. - The release workflow requires the
HOMEBREW_TAP_GITHUB_TOKENsecret with permission to push branches and open PRs inblackmichael/homebrew-tap.
Repo Shape
src/App.tsxApp shell, providers, router, global quit handling.src/screensTop-level screens: login, timeline, post detail, profile.src/componentsShared terminal UI components like post cards, reply lists, profile header, status bar.src/apiThin wrappers around@atproto/api.src/stateContext/reducer state for auth, navigation, and timeline.src/libPure helpers and unit tests. Prefer putting logic here when it can be tested outside the terminal renderer.
Working Norms
- Keep terminal layout deterministic. Dynamic wrapping can easily break row budgeting and hide engagement rows.
- Prefer fixed-height or explicitly budgeted list rows for scrolling UIs.
- When changing list rendering, check both timeline and reply list behavior.
- Keep shared rendering pieces shared.
Examples:
PostMeta,PostEngagement,ProfileMeta,ProfileEngagement. - For behavior-heavy changes, extract pure helpers into
src/liband addbun testcoverage.
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.
- 2d ago First seen · 136 lines · 1,207 tokens per session scan A d38bc550e2fd
tuisky AGENTS.md is an instructions file published in the GitHub repository blackmichael/tuisky (5 stars, last pushed 2mo ago), licensed MIT. It adds 1,207 tokens to every session, about $0.0060 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
atproto-skills CLAUDE.md
Instructions for ngerakines/atproto-skills, covering authoring guide: atproto-skills, 1. skill anatomy, polyglot skills (optional shape), 2. progressive disclosure and 3. writing effective description fields.
bluesky-mcp AGENTS.md
AGENTS.md instructions for sandraschi/bluesky-mcp, covering bluesky-mcp — agent guide, standards, key files and quick ref.
bluesky-mcp CLAUDE.md
Claude Code instructions for sandraschi/bluesky-mcp, covering bluesky-mcp — claude / agent context, do, don't and commands.
wordpress-atmosphere AGENTS.md
AGENTS.md instructions for Automattic/wordpress-atmosphere, covering atmosphere plugin, directory structure, commands, environment and php tests (require wp-env running).
bluesky-mcp copilot-instructions.md
Copilot instructions for sandraschi/bluesky-mcp, covering github copilot instructions for bluesky-mcp and session context (bluesky mcp).
skyreader AGENTS.md
AGENTS.md instructions for disnet/skyreader, a project described as: An RSS reader for the AT Protocol.