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 paulieb89/property-shared --skill add-data-sourcegit clone --depth 1 https://github.com/paulieb89/property-sharedWrote 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/paulieb89/property-shared/add-data-source)<a href="https://agentmods.dev/skills/paulieb89/property-shared/add-data-source"><img src="https://agentmods.dev/badge/skills/paulieb89/property-shared/add-data-source/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/paulieb89/property-shared/add-data-source"><img src="https://agentmods.dev/badge/skills/paulieb89/property-shared/add-data-source.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00038 | $0.00753 |
| Opus 5.5 | $0.00015 | $0.00301 |
| Sonnet 5.5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
add-data-source 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a New Data Source
Follow these 6 steps in order. Each step must be completed before moving to the next.
Step 1: Create Transport Client
Create property_core/new_client.py. Choose the pattern that fits:
- Sync HTTP API (httpx): see
property_core/companies_house_client.pyis_configured()check for optional credentials- Basic auth or API key from
os.getenv()
- Async HTTP API (httpx): see
property_core/epc_client.py - HTML scraper (requests + BeautifulSoup): see
property_core/rightmove_scraper.py - SPARQL/RDF: see
property_core/ppd_client.py
Required in all clients:
from __future__ import annotations- Type hints on all methods
- Docstring on the class/module
- Rate limiting/retry logic where appropriate
Step 2: Create Pydantic Models
Create property_core/models/new_source.py.
Transport-parsed models get the raw field:
raw: dict | None = Field(default=None, exclude=True)
Use @classmethod factory methods for parsing:
@classmethod
def from_api_response(cls, data: dict) -> "NewModel":
return cls(field=data.get("key"), raw=data)
Step 3: Export from models/init.py
Open property_core/models/__init__.py:
- Add import:
from .new_source import NewModel - Add to
__all__list
Step 4: Export from property_core/init.py
Open property_core/__init__.py:
- Add client/service import
- Add model import
- Add both to
__all__list
Step 5: Create Domain Service (if needed)
If the data source needs orchestration (combining with other sources, stats computation, guardrails), create property_core/new_service.py.
- Class-based if stateful:
class NewService - Function-based if stateless:
def analyze_new() - Export from
property_core/__init__.py
Step 6: Add Consumer Endpoints
All three consumers must be updated:
API Router
Create app/api/v1/new_source.py, register in app/api/routes.py.
See /add-endpoint skill for details.
MCP Tool
Add @mcp.tool() function in mcp_server/server.py.
See /add-mcp-tool skill for details.
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 Changed 701dd2858156
- 1mo ago First seen · 91 lines · 38 tokens per session scan A 671c06675591
add-data-source is a skill published in the GitHub repository paulieb89/property-shared (18 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 753 once invoked, about $0.0002 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
api-architect
Design and build production-grade RESTful and GraphQL APIs with proper authentication, error handling, rate limiting, and documentation. Use when designing APIs, creating API specifications, or reviewing API architecture.
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…
sanity-singletons
Configure singleton documents in a Sanity Studio using the document.singletons registry. Use when a developer wants a fixed-id document (settings, navigation, footer) edited in place, hidden from the default content list, with no "create new" or "duplicate" affordances — or when migrating a userland singleton…
sanity-best-practices
Sanity development best practices for schema design, GROQ queries, TypeGen, Visual Editing, images, Portable Text, Studio structure, localization, migrations, Sanity Functions, webhooks, Blueprints, and framework integrations such as Next.js, Nuxt, Astro, Remix, SvelteKit, Angular, Hydrogen, the App SDK, and Studios…
agent-communication-protocol-enuno-claude-command-and-c-2
This page used to hold an archived copy of this skill. The archive now lives in the registry's data repository.