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 zgbrenner/agentcounsel --skill title-survey-objection-trackergit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/title-survey-objection-tracker)<a href="https://agentmods.dev/skills/zgbrenner/agentcounsel/title-survey-objection-tracker"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/title-survey-objection-tracker/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/zgbrenner/agentcounsel/title-survey-objection-tracker"><img src="https://agentmods.dev/badge/skills/zgbrenner/agentcounsel/title-survey-objection-tracker.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.00029 | $0.02298 |
| Opus 5 | $0.00015 | $0.01149 |
| Sonnet 5 | $0.00006 | $0.00460 |
| Haiku 4.5 | $0.00003 | $0.00230 |
Grade A, and why
Title and Survey Objection Tracker 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Title and Survey Objection Tracker
Purpose
Organize the exceptions raised in a title commitment or title report, together with the matters shown on a survey, into a single structured tracker that an attorney or transaction team can use as a working diligence reference. The tracker condenses Schedule B exceptions, recorded encumbrances, and survey notes into a navigable list in which every item traces to a specific exception number, schedule, page, or survey reference.
This skill produces draft work product for attorney review only. It is not legal advice. The tracker is an organizing tool; the title commitment, the exception documents, and the survey themselves always control.
Use When
- A user asks to "track the title objections," "organize the Schedule B exceptions," or "build an objection list from this title commitment and survey."
- A transaction team needs a structured reference for the exceptions and survey matters on a parcel under contract or under review.
- Title and survey items must be organized as part of acquisition, financing, or development diligence.
- An objection tracker is needed as an input to a purchase and sale agreement review or a closing deliverables checklist.
Required Inputs
- The title commitment or title report — uploaded or pasted, including Schedule A, Schedule B-I (requirements), and Schedule B-II (exceptions). Do not work from a description, a partial excerpt, or a prior summary.
- The underlying exception documents — recorded easements, covenants, liens, plats, and similar — if available. Note which were and were not provided.
- The survey — if available — including the surveyor's notes and table of matters.
- The party role the tracker is prepared for — buyer, seller, borrower, lender, or developer.
- The parcel(s) at issue — the legal description, tax parcel number, or street address each item relates to.
If the title commitment or report is not provided, stop and request it. Do not build a tracker from a document you have not been given.
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 · 203 lines · 29 tokens per session scan A 5725150874ed
Title and Survey Objection Tracker is a skill published in the GitHub repository zgbrenner/agentcounsel (19 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 2,298 once invoked, about $0.0001 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-03.
Other skills, from other repositories
legal-research
A legal research skill for finding and analysing laws and court cases, including similar cases. It requires access to a reliable legal research database before producing a formal report.
document-fill
A document-filling assistant that uses a supplied template and case files to fill in forms, contracts, or legal documents. It also reports where each filled value came from and which details are missing.
contract-review
A contract-review workflow for agreements governed by Chinese law, United States law, or both. It examines clauses one by one and produces a list of legal-risk questions, with an optional marked-up Word document.
fedramp
Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document…
eu-cra
Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 — mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route…
aenderungsvorbehalt-308
Für Änderungsvorbehalt 308: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt.