API_TOPICS_DOC

API_TOPICS_DOC is a cursor rule for Cursor from nicekon/zendesk-mcp-server-kon. It costs 51 tokens per session (1,433 once invoked), scanned B, original, Apache-2.0.

Reference rules for Zendesk community topics, which group related help-center posts under a subject. They describe topic fields, permissions, and API behavior.

In plain words
What is it for?
Use them when creating, viewing, updating, or deleting Zendesk community topics.
Why use it?
They make it easier to understand which topic data can be changed and who is allowed to manage it.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Install

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.

agentmods
npx agentmods add rules/nicekon/zendesk-mcp-server-kon/api_topics_doc
Clone the repo
git clone --depth 1 https://github.com/nicekon/zendesk-mcp-server-kon

Made for: Cursor.

Wrote 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.

agentmods badge for API_TOPICS_DOC

README.md
[![agentmods](https://agentmods.dev/badge/rules/nicekon/zendesk-mcp-server-kon/api_topics_doc.svg)](https://agentmods.dev/rules/nicekon/zendesk-mcp-server-kon/api_topics_doc)
Your own site
<a href="https://agentmods.dev/rules/nicekon/zendesk-mcp-server-kon/api_topics_doc"><img src="https://agentmods.dev/badge/rules/nicekon/zendesk-mcp-server-kon/api_topics_doc.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,433 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.01433
Opus 5 $0.00026 $0.00717
Sonnet 5 $0.00010 $0.00287
Haiku 4.5 $0.00005 $0.00143

Measured 5d ago against content hash 66c895801de7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade B, and why

API_TOPICS_DOC scanned grade B with 2 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 5d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

curl curl -v -u {email_address}/token:{api_token} -d '{"topic": {"name": "Help Center-Tricks Updated"}}' \

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl
.cursor/rules/API_TOPICS_DOC.mdc · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Topics A topic represents a collection of community posts on a subject.

JSON format Topics are represented as JSON objects with the following properties:

Name Type Read-only Mandatory Description created_at string true false When the topic was created description string false false The description of the topic. By default an empty string follower_count integer true false The number of users following the topic html_url string true false The community url of the topic id integer true false Automatically assigned when the topic is created manageable_by string false false The set of users who can manage this topic. Allowed values are "staff", or "managers". name string false true The name of the topic position integer false false The position of the topic relative to other topics in the community updated_at string true false When the topic was last updated url string true false The API url of the topic user_segment_id integer false false The id of the user segment to which this topic belongs The manageable_by attribute takes one of the following values:

Value Users staff agents and managers managers only Help Center managers Note that manageable_by is only displayed to users who can manage the topic.

Example { "created_at": "2012-04-04T09:14:57Z", "description": "Security Best Practices", "follower_count": 332, "id": 1635, "manageable_by": "staff", "name": "Security" } List Topics GET /api/v2/community/topics Lists all topics.

Allowed for Anonymous users Pagination Cursor pagination (recommended) Offset pagination See Pagination.

Code Samples curl curl https://{subdomain}.zendesk.com/api/v2/community/topics.json
-v -u {email_address}/token:{api_token} Go Java Nodejs Python import requests from requests.auth import HTTPBasicAuth

url = "https://support.zendesk.com/api/v2/community/topics" headers = { "Content-Type": "application/json", } email_address = 'your_email_address' api_token = 'your_api_token'

Use basic authentication

auth = HTTPBasicAuth(f'{email_address}/token', api_token)

response = requests.request( "GET", url, auth=auth, headers=headers )

print(response.text) Ruby Example response(s) 200 OK Show Topic GET /api/v2/community/topics/{topic_id} Shows information about a single topic.

Allowed for Anonymous users Parameters Name Type In Required Description topic_id integer Path true The unique ID of the topic Code Samples curl curl https://{subdomain}.zendesk.com/api/v2/community/topics/{topic_id}.json
-v -u {email_address}/token:{api_token} Go Java Nodejs Python import requests from requests.auth import HTTPBasicAuth

url = "https://support.zendesk.com/api/v2/community/topics/360001326113" headers = { "Content-Type": "application/json", } email_address = 'your_email_address' api_token = 'your_api_token'

Read the full file on GitHub · 236 lines

Changes

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.

  1. 5d ago First seen · 236 lines · 51 tokens per session scan B 66c895801de7

Subscribe to this mod's changes

API_TOPICS_DOC is a cursor rule published in the GitHub repository nicekon/zendesk-mcp-server-kon (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 1,433 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.