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 ThomasMoreAI/legal-skills-open --skill land-title-verifier-wutsigit clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/land-title-verifier-wutsi)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/land-title-verifier-wutsi"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/land-title-verifier-wutsi/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/thomasmoreai/legal-skills-open/land-title-verifier-wutsi"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/land-title-verifier-wutsi.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.00023 | $0.00478 |
| Opus 5.5 | $0.00009 | $0.00191 |
| Sonnet 5.5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
land-title-verifier-wutsi 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- land-title-verifier — 95% identical, 8 lines differ
What it actually says
Skill: Land Title Verifier
This skill allows the agent to check the authenticity of a "Titre Foncier" (Land Title) in Cameroon. It should be used whenever a user provides a title number or asks for property verification.
Tools
-
check_title: Queries the digital land registry database.title_number: (string) The unique ID of the land title (e.g., "1234/LIT").region: (string) Optional. The administrative region, such as "Littoral", "Centre", or "Ouest".
-
get_title_history: Return the chain of previous owners for a given title number.title_number: (invalid_type) The unique ID of the land title (e.g., "1234/LIT").
Instructions
- Verification Protocol: If a title is found, always report the "Nom du Propriétaire" (Owner Name) and the " Superficie" (Area in square meters).
- Fraud Detection: If the title number does not match the expected regional format (e.g., missing the region suffix), flag it as "Suspicious" and suggest a physical "Concierge Verification."
- Tone: Maintain a professional, legalistic tone. Use French terminology for official document names (e.g., " Certificat de Propriété") but keep the summary in the user's preferred language.
Examples
User: "Can you check land title 5678/LIT in Douala?"
Action: Call check_title(title_number="5678/LIT", region="Littoral")
User: "I want to see the history of this property: 9912/CEN."
Action: Call get_title_history(title_number="9912/CEN")
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.
- 1mo ago First seen · 45 lines · 23 tokens per session scan A ee3f42aea7cd
land-title-verifier-wutsi is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 23 tokens to every session and 478 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…