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/fry69/altq.net/gemini-mdgit clone --depth 1 https://github.com/fry69/altq.netWrote 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/fry69/altq.net/gemini-md)<a href="https://agentmods.dev/instructions/fry69/altq.net/gemini-md"><img src="https://agentmods.dev/badge/instructions/fry69/altq.net/gemini-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.00715 | $0.00715 |
| Opus 5 | $0.00358 | $0.00358 |
| Sonnet 5 | $0.00143 | $0.00143 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
altq.net GEMINI.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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Identity
Type: Infrastructure-as-Code (IaC) Deployment Template
Description: This repository is a deployment template for a remote server environment. It is NOT a standard software application with a build step.
Context: Many configuration files (e.g., pds.env, *.j2) are redacted or templated. These should be treated as placeholders or intended for runtime substitution, not as syntax errors or missing secrets.
Stack Detection
Container Services:
- Caddy (v2) - Web Server & Reverse Proxy
- PDS (Bluesky Personal Data Server) - Core Service
- Watchtower - Container Auto-updater
- Gatekeeper - Access Control Sidecar
Orchestration & Tools:
- Ansible Core - Configuration Management
- Docker Compose (v3.9) - Container Orchestration
- Systemd - Service Management (Host level)
- Python 3 - Status Generation Scripting
- Bash - Helper Scripts
Safety Protocols
[!IMPORTANT] High Caution Execution Policy Agents must NEVER auto-execute the following without explicit user confirmation:
- Ansible Playbooks (
ansible-playbook,*.yml)- Shell Scripts (
*.sh) that modify system state- Docker Compose commands that alter running containers
Always ask for approval before running commands that modify the remote server state.
File Classification
Active (Orchestration & Scripts):
site.yml- Main Ansible Playbook for deployment.Makefile- Convenience wrapper for Ansible commands (primary interface).bin/generate-status.py- Python script for generating status reports.
Passive (Configuration & Definitions):
compose.yaml- Docker Compose service definitions.caddy/etc/Caddyfile- Caddy web server configuration.ansible/group_vars/all.yml- Global Ansible variables.ansible/templates/*.j2- Jinja2 templates for systemd units.pds.env/pds.redacted.env- Environment variable definitions.
Operation Mapping
| User Intent | Mapped Command | Context |
|---|---|---|
| Run / Deploy Project | make deploy |
Full deployment via Ansible (ansible-playbook site.yml). |
| Dry Run / Preview Changes | make dry-run |
Shows what would change without applying (--check --diff). |
| Update Caddy Config | make caddy |
Updates Caddy config & webroot only (--tags caddy). |
| Update Status Script | make status-script |
Updates status script & systemd units (--tags status). |
| Restart PDS Service | make restart |
Restarts the PDS systemd service (--tags pds -e pds_restart=true). |
| Generate Status Page | make generate |
Manually triggers status page generation (--tags status,run_once). |
| Check PDS Health | make version |
Checks PDS health endpoint (--tags health). |
| Check Service Status | make status |
Checks PDS systemd service status (via ansible pds -a). |
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 · 64 lines · 715 tokens per session scan A 8eb0aa926192
altq.net GEMINI.md is an instructions file published in the GitHub repository fry69/altq.net (12 stars, last pushed 6mo ago), licensed MIT. It adds 715 tokens to every session, about $0.0036 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-09-02.
Other instructions, from other repositories
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).
tuisky AGENTS.md
Instructions for blackmichael/tuisky, covering agents.md, purpose, tech stack, core commands and release flow.
bluesky-mcp copilot-instructions.md
Copilot instructions for sandraschi/bluesky-mcp, covering github copilot instructions for bluesky-mcp and session context (bluesky mcp).
wordpress-atmosphere CLAUDE.md
Claude Code instructions for Automattic/wordpress-atmosphere, a project described as: ATmosphere connects your WordPress site to the AT Protocol network. When you publish a post, it is automatically cross-posted to Bluesky and registered as a standard.site document on your Personal Data Server (PDS).