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 manzoor-source/teradata-mcp-server-stc --skill teradata-mcp-customisationgit clone --depth 1 https://github.com/manzoor-source/teradata-mcp-server-stcWrote 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/manzoor-source/teradata-mcp-server-stc/teradata-mcp-customisation)<a href="https://agentmods.dev/skills/manzoor-source/teradata-mcp-server-stc/teradata-mcp-customisation"><img src="https://agentmods.dev/badge/skills/manzoor-source/teradata-mcp-server-stc/teradata-mcp-customisation/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/manzoor-source/teradata-mcp-server-stc/teradata-mcp-customisation"><img src="https://agentmods.dev/badge/skills/manzoor-source/teradata-mcp-server-stc/teradata-mcp-customisation.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.00090 | $0.01746 |
| Opus 5 | $0.00045 | $0.00873 |
| Sonnet 5 | $0.00018 | $0.00349 |
| Haiku 4.5 | $0.00009 | $0.00175 |
Grade A, and why
teradata-mcp-customisation scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
6. **Smoke-test the server** with the MCP listing flow before pointing a client at it. See `reference/deployment.md` for the bash curl recipe (`initialize` → `notifications/initialized` → `tools/list`). This is a copy
100% identical to teradata-mcp-customisation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are extending the Teradata MCP server with a semantic layer: domain-specific tools, cubes, prompts, and glossary terms declared in YAML files that the server picks up at startup.
The server is the upstream project at https://github.com/Teradata/teradata-mcp-server. The customisation surface is documented in docs/server_guide/CUSTOMIZING.md; this skill compiles the parts that are easy to get wrong, plus working examples that anyone can run against the DBC system database.
When to use this skill
- Designing a new semantic layer for a Teradata data product (cubes + curated prompts).
- Adding or editing a custom tool / cube / prompt / glossary entry.
- Building a
profiles.ymlto expose a subset of objects to a given client. - Debugging why a custom object does not appear in
tools/list,prompts/list, orresources/list. - Migrating a hand-written SQL pattern into a reusable cube the LLM can compose.
Mental model — what each object becomes at runtime
YAML type: |
Where it surfaces | Selected by profile section |
|---|---|---|
tool |
MCP tool — parameterised SQL the LLM calls | tool: |
cube |
MCP tool — the server auto-generates a 6-arg aggregator (dimensions, measures, filter, res_filter, order_by, top) plus any custom params you declare | tool: |
prompt |
MCP prompt — a reusable system / user prompt the client can fetch by name | prompt: |
glossary |
MCP resource — domain terms surfaced as context resources, enriched with cube measure/dim descriptions | resource: |
There is no type: resource. Resources are derived: glossary entries become resources, and cube/tool descriptions feed back into glossary enrichment.
Workflow
- Locate the config directory. The server reads YAML from
--config_dir(CLI) or$CONFIG_DIR(env), defaulting to the current working directory. Drop one or more*.ymlfiles there alongsideprofiles.yml. Multiple files merge into one namespace keyed by object name. - Pick the object type for what you are building. If in doubt, see
reference/object-types.md. - Write the SQL first, in isolation. Run it in your usual Teradata client until it returns what you want — then wrap it as a tool or cube. For cubes, write the flat denormalised base SQL; let the server build the aggregator on top. See
reference/cube-mechanics.mdfor exactly how the wrapping works (which is critical for understanding filter vs res_filter semantics). - Get parameter substitution right. Custom tools support two styles:
:paramfor value binds,{param}for identifier interpolation (database / table names). Cubes also accept custom parameters used inside the base SQL the same way. Seereference/parameter-substitution.md. - Expose via
profiles.yml. Add a profile (or extend an existing one) with regex selectors. Seereference/profiles.mdfor the layering rules and the built-in profiles you can inherit from. - Smoke-test the server with the MCP listing flow before pointing a client at it. See
reference/deployment.mdfor the bash curl recipe (initialize→notifications/initialized→tools/list).
What ships with it
10 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.
- examples/example_cube.yml 11 KB
- examples/example_glossary.yml 1.9 KB
- examples/example_profiles.yml 1.6 KB
- examples/example_prompt.yml 2.0 KB
- examples/example_tool.yml 1.8 KB
- reference/cube-mechanics.md 5.4 KB
- reference/deployment.md 4.1 KB
- reference/object-types.md 7.8 KB
- reference/parameter-substitution.md 5.1 KB
- reference/profiles.md 4.5 KB
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.
- 9d ago First seen · 70 lines · 90 tokens per session scan A 9e8c98055274
teradata-mcp-customisation is a skill published in the GitHub repository manzoor-source/teradata-mcp-server-stc (0 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 1,746 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to teradata-mcp-customisation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.