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 Lingtai-AI/lingtai --skill repo-watchgit clone --depth 1 https://github.com/Lingtai-AI/lingtaiWrote 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/lingtai-ai/lingtai/repo-watch)<a href="https://agentmods.dev/skills/lingtai-ai/lingtai/repo-watch"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/repo-watch/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/lingtai-ai/lingtai/repo-watch"><img src="https://agentmods.dev/badge/skills/lingtai-ai/lingtai/repo-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 92 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00083 | $0.01096 |
| Opus 5 | $0.00042 | $0.00548 |
| Sonnet 5 | $0.00017 | $0.00219 |
| Haiku 4.5 | $0.00008 | $0.00110 |
Grade A, and why
dev-guide-repo-watch 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 13d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LingTai Repo Watch
This nested lingtai-dev-guide reference is a read-only developer workflow for
sweeping the Lingtai-AI GitHub org. It lives here because it is
LingTai-project-specific; it should not be installed as a kernel intrinsic
capability for every agent.
Boundaries
- Read-only by default: do not comment, label, assign, close, merge, or edit GitHub state unless the human explicitly asks for that side effect.
- Report facts with source URLs and timestamps.
- Prefer one concise digest over piecemeal alerts unless the human requested a live monitor.
- If automating, store state locally and alert only on changes to avoid spam.
One-shot org sweep
Use gh from a clean shell with GitHub auth already configured.
gh repo list Lingtai-AI --limit 100 \
--json name,visibility,isArchived,pushedAt,url
gh search issues --owner Lingtai-AI --state open --limit 200 \
--json number,title,repository,state,createdAt,updatedAt,author,labels,assignees,url
gh search prs --owner Lingtai-AI --state open --limit 200 \
--json number,title,repository,state,isDraft,createdAt,updatedAt,author,labels,url
gh search prs --json does not support reviewDecision on all installed gh
versions. If review-decision status is needed, fetch it separately for a small
set of PRs with a command/API that supports that field; do not put
reviewDecision in the broad gh search prs field list unless you have verified
that local gh supports it.
Optional filters
For "non-self" monitoring, filter after fetching rather than hard-coding a single human into this workflow. Example for Jason's machine:
# Conceptual filter after JSON fetch, not a GitHub write:
author.login != "huangzesen"
Digest shape
Group output in this order:
- New or updated open PRs — ready vs draft, author, repo, age, URL.
- Open issues — repo, title, author, labels, stale/updated time, URL.
- Recently merged/closed items if the caller asked for recent activity.
- Stale or blocked items — old open PRs, no assignee, labels implying bug or release blocker.
- No-action footer — say explicitly that no GitHub state was changed.
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.
- 13d ago First seen · 108 lines · 83 tokens per session scan A 7bab783be3c4
dev-guide-repo-watch is a skill published in the GitHub repository Lingtai-AI/lingtai (677 stars, last pushed yesterday), licensed Apache-2.0. It adds 83 tokens to every session and 1,096 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-30.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.