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 Tx1207/hello-scholar --skill landinggit clone --depth 1 https://github.com/Tx1207/hello-scholarWrote 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/tx1207/hello-scholar/landing)<a href="https://agentmods.dev/skills/tx1207/hello-scholar/landing"><img src="https://agentmods.dev/badge/skills/tx1207/hello-scholar/landing.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.00069 | $0.01653 |
| Opus 5 | $0.00034 | $0.00826 |
| Sonnet 5 | $0.00014 | $0.00331 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
landing 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 7d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Landing
Overview
Enter landing only when the user explicitly expresses Landing intent in this turn. Existing takeoff context is input, not authorization; without that authorization, stay in the current phase. A valid intent either names landing or explicitly asks to reality-test a direction by making it feasible, grounding or shrinking it, and defining a stop rule.
landing rewrites the bold direction into a feasible plan: keep the ambition, rewrite the parts that cannot survive reality, and produce a feasible revised direction. The output is not just the first move and not the whole execution plan.
If brainstorming also applies, deliver the landing judgment first before any brainstorming-style clarification begins. Brainstorming starts only after the user accepts the landed direction or explicitly asks to refine it. When design work is next, ask the user whether to enter brainstorming; wait for their answer before changing phase.
After entry is authorized, recover the prior direction from current context. A valid context makes the bold thesis, the old model it replaces, and the main reality question recoverable. If an explicit Landing request lacks those inputs, ask for the missing direction; explicit intent does not permit guessing the thesis. Ordinary risk, MVP, verification, or next-step questions do not authorize Landing.
Entry Check
Before reading the Workflow, quote the user's triggering words from this turn. A future Approved Task may authorize entry only if an explicit contract adds that path. If there is no explicit Landing intent, stay in the current phase and do not read the workflow below to self-trigger. Once authorized, verify that the bold thesis, old model, and main reality question are recoverable; otherwise ask the one missing-direction question before using any template. Complete this check only with an authorization quote plus recoverable direction, or with that missing-input question.
Value Criteria
This is the landing value gate, not decoration. Every important Must Keep or Rewrite and Keep item must name the criterion it hits and the concrete payoff. If it cannot, default to Defer or Delete. "Already exists", "the user likes it", or "easy to change" is not value.
What ships with it
3 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.
- 7d ago First seen · 62 lines · 69 tokens per session scan A 667f2b897e20
landing is a skill published in the GitHub repository Tx1207/hello-scholar (5 stars, last pushed 26d ago), licensed MIT. It adds 69 tokens to every session and 1,653 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…