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-endpointgit 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-endpoint)<a href="https://agentmods.dev/skills/paulieb89/property-shared/add-endpoint"><img src="https://agentmods.dev/badge/skills/paulieb89/property-shared/add-endpoint.svg" alt="Measured on agentmods" 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.00027 | $0.00501 |
| Opus 5 | $0.00014 | $0.00251 |
| Sonnet 5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
add-endpoint 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 8d 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.
What it actually says
Add an API Endpoint
API routers are thin HTTP wrappers — all business logic lives in property_core.
Step 1: Create Router File
Create app/api/v1/new_endpoint.py:
from __future__ import annotations
from fastapi import APIRouter, HTTPException, Query
router = APIRouter(prefix="/new", tags=["new"])
@router.get("/action")
async def action_endpoint(
required: str = Query(..., description="Required parameter"),
optional: str | None = Query(None, description="Optional filter"),
limit: int = Query(50, ge=1, le=200, description="Max results"),
):
"""Endpoint description."""
import asyncio
from property_core import SomeService
try:
result = await asyncio.to_thread(
SomeService().method,
param=required,
limit=limit,
)
except ValueError as exc:
raise HTTPException(status_code=422, detail=str(exc))
return result.model_dump(mode="json")
Step 2: Register in routes.py
Open app/api/routes.py:
from .v1 import new_endpoint
api_router.include_router(new_endpoint.router)
Step 3: Response Model (optional)
- Prefer returning
property_coremodels directly (Pydantic → JSON automatic) - If you need an envelope, add to
app/schemas/new_endpoint.py - Re-export from
app/schemas/__init__.pyif needed
Patterns
| Pattern | Example |
|---|---|
| Sync service call | app/api/v1/ppd.py |
| Async service call | app/api/v1/analysis.py |
| Simple calculator | app/api/v1/stamp_duty.py |
| Configuration check | app/api/v1/epc.py |
Checklist
- Router file created in
app/api/v1/ - Router registered in
app/api/routes.py - No business logic in the router (property_core handles that)
-
Query()annotations with descriptions on all parameters - Error handling:
ValueError→ 422, upstream failure → 502
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.
- 8d ago First seen · 75 lines · 27 tokens per session scan A 82e3a7cfc1f4
add-endpoint is a skill published in the GitHub repository paulieb89/property-shared (16 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 501 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-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…
agent-communication-protocol
Open protocol for AI agent interoperability enabling standardized communication between agents, applications, and humans across different frameworks.
csharp-patterns
C#/.NET: LINQ, async/await, DI, records, nullable refs, ASP.NET Core, EF Core, MediatR. Triggers: C#, .NET, dotnet, ASP.NET, EF Core, LINQ, record type, IServiceCollection.
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, and the App SDK. Use this…