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 skills add YuanASI/guijios-skills --skill guijios-replygit clone --depth 1 https://github.com/YuanASI/guijios-skillsWrote 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/skills/yuanasi/guijios-skills/guijios-reply)<a href="https://agentmods.dev/skills/yuanasi/guijios-skills/guijios-reply"><img src="https://agentmods.dev/badge/skills/yuanasi/guijios-skills/guijios-reply/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/yuanasi/guijios-skills/guijios-reply"><img src="https://agentmods.dev/badge/skills/yuanasi/guijios-skills/guijios-reply.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.02806 |
| Opus 5 | $0.00037 | $0.01403 |
| Sonnet 5 | $0.00015 | $0.00561 |
| Haiku 4.5 | $0.00007 | $0.00281 |
Grade A, and why
guijios-reply 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 11d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-platform reply/comment drafting. Auto-routes to the correct platform ruleset based on input.
Routing
| Input | Mode |
|---|---|
| GitHub Issue/PR number or link | GitHub mode |
| Reddit comment text/screenshot | Reddit mode |
| Twitter/X content | Twitter mode |
| Other platforms or unspecified | General mode (applies universal principles) |
Part 1: Universal Principles (Shared Across All Platforms)
Context Assessment (Judge Before Writing)
| Context | Definition | Core Strategy |
|---|---|---|
| Your turf | You are the maintainer / OP / author | Deliver information |
| Someone else's turf | You are a visitor | Contribute experience first, then ask; no self-promotion |
| Cold DM | Zero prior relationship, you're reaching out | Reference their specific content to build trust |
Rules for Someone Else's Turf
- Contribute before asking. Share a similar problem or experience, then naturally lead into one question
- One question per comment. Multiple questions = interrogation vibes
- Every question must have clear information value. Before posting, articulate "what will this answer tell me?" If you can't, rewrite
- Your profile is your introduction. No need to introduce yourself in the body text
- Don't reveal research intent. Look like "someone who ran into the same problem," not "competing founder mining for intel"
Rules for Cold DMs
- Quote their specific words. Vague references = low reply rate
- Make it clear you're not selling anything
- Give them an easy out. "No worries if not"
- Async over calls. Higher reply rate
Pre-Send Checklist (5 Steps, Required Every Time)
- Intent check: What information does this comment aim to get? What's the concrete use for us? If you can't answer, rewrite
- Fact check: Verify your own project's technical claims against code; verify quotes against originals
- Smell check: Re-read from the recipient's perspective. Does it read like competitive research? Like AI? Or like someone who naturally ran into the same problem?
- Style check: Run through the blocklist
- Compression check: Can you cut an entire paragraph? Can bullets collapse into prose? Did you restate something the other person already said clearly? When in doubt, cut
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 306 lines · 74 tokens per session scan A 2ac13c0b025f
guijios-reply is a skill published in the GitHub repository YuanASI/guijios-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 2,806 once invoked, about $0.0004 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 skills, from other repositories
investigating-builds
Use when the user is working with an existing Buildkite CI run and wants to understand, diagnose, or act on it. Strong signals: a buildkite.com URL, the word "buildkite", the bk CLI, the bktide tool, or a reference to a specific pipeline, build, or job. Covers intents like: "why did this build fail", "what's flaking"…
scope
Guide for working with Scope, a developer environment management tool that automates environment checks, detects known errors, and provides automated fixes. Use when creating Scope configurations (ScopeKnownError, ScopeDoctorGroup, ScopeReportLocation), debugging environment issues, or writing rules for error…
harness-binary-spelunking
Use when investigating an agent-harness CLI's internals (Claude Code, codex, opencode, or similar): extracting the system prompt or tool descriptions, finding what code path produces a specific UI message, decoding minified function names or Rust symbols, understanding undocumented config keys, or otherwise spelunking…
park
Save current work context for later resumption.
developing-pipelines
Use when creating, modifying, or debugging Buildkite pipeline YAML files - ensures current syntax from official docs, validates configurations before proposing changes, and references Buildkite best practices instead of relying on training data.
fixing-ci
Use when CI is failing on a branch, PR, or specific Buildkite build and the user wants to iteratively fix it through verify-locally → push → check → iterate. Strong signals: "fix CI", "make CI green", "CI is failing", "tests are failing in Buildkite", "iterate on this build", a Buildkite build URL paired with intent…