What is code-contribution?

A contribution guide for adding code to Agent Topic Lab. It explains the project’s frontend and backend locations, commit-message format, and expected checks.

Implementing features, fixing bugs, adding tests, preparing pull requests, and following the project’s commit and verification workflow.

It reduces uncertainty about where changes belong, how commits should be named, and how to check that a contribution builds or tests correctly.

How TashanGKD/Tashan-TopicLab configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to TashanGKD/Tashan-TopicLab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/TashanGKD/Tashan-TopicLab/main/.cursor/skills/code-contribution/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/TashanGKD/Tashan-TopicLab

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tashangkd/tashan-topiclab/code-contribution/github.svg)](https://agentmods.dev/skills/tashangkd/tashan-topiclab/code-contribution)

Your own site

<a href="https://agentmods.dev/skills/tashangkd/tashan-topiclab/code-contribution"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-topiclab/code-contribution/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tashangkd/tashan-topiclab/code-contribution"><img src="https://agentmods.dev/badge/skills/tashangkd/tashan-topiclab/code-contribution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,227 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.01227
Opus 5.5	$0.00018	$0.00491
Sonnet 5.5	$0.00009	$0.00245
Haiku 4.5	$0.00005	$0.00123

Measured 1mo ago against content hash c4668a4ee895, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-contribution 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.

.cursor/skills/code-contribution/SKILL.md · 117 lines

How it starts

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

Code Contribution Guide

When contributing code to Agent Topic Lab, follow this workflow.

Project Structure

Frontend: frontend/ — React 18 + TypeScript + Vite
Backend: backend/ — Resonnet submodule (FastAPI, Python 3.11+)

Commit Convention

Use Conventional Commits:

<type>(<scope>): <short description>

[optional body]

Types: feat, fix, docs, refactor, test, chore

Scopes (preferred):

frontend — UI, components, pages, API client
api — Backend API routes (in backend/app/api/)
agent — Backend agent logic (in backend/app/agent/)
posts, topics, experts, moderator — Domain-specific

Examples:

feat(frontend): add reply button to post thread
fix(api): handle empty body in mention reply
docs(readme): add backend link to Resonnet
test(api): add 404 cases for topic experts
chore: update backend submodule

Rules:

Lowercase subject; no period at end
Breaking changes: feat(api)!: remove deprecated field

Unit Tests

Frontend

Run: cd frontend && npm test (if test script exists)
Lint: cd frontend && npm run build (TypeScript + Vite)
Follow existing component patterns; new logic should have tests when feasible

Backend (Resonnet)

Required: New or changed logic must have corresponding tests
Run before PR: cd backend && pytest -q -m "not integration"
CI: Must pass unit tests
Fixtures: Use tmp_path for isolated workspace; monkeypatch.setenv("WORKSPACE_BASE", ...)
API tests: See backend/tests/API_TEST_GUIDE.md

Integration tests (Agent SDK):

Mark with @pytest.mark.integration and @pytest.mark.slow
Require real .env; ANTHROPIC_API_KEY must not be test
Run: cd backend && pytest tests/test_agent_sdk.py -m integration -v -s
Full local CI: cd backend && bash scripts/ci_local.sh

Read the full file on GitHub · 117 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.

1mo ago First seen · 117 lines · 46 tokens per session scan A c4668a4ee895

Subscribe to this mod's changes

code-contribution is a skill published in the GitHub repository TashanGKD/Tashan-TopicLab (6 stars, last pushed 10d ago), licensed MIT. It adds 46 tokens to every session and 1,227 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-31.

Code review Git and workflow Multi-Agent airesearch moltbook resonnet

guardian

Gatekeeping Git/PR by classifying change essence and recommending granularity, naming, and strategy; the ship recipe also executes PR delivery (create, CI watch, merge, cleanup) with Ask First on merge. Use when PR preparation, commit strategy, or gated PR delivery is needed.

simota/agent-skills · 62 tokens

deploy-landed

A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.

avelikiy/great_cto · 103 tokens

signing-preflight

Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…

avelikiy/great_cto · 105 tokens

harness-pr-reviewer

Checks a submitted PR against the environment's baseline assets (CLAUDE.md, memory, naming, asset classification) and attaches a review comment with a merge recommendation. 5 steps — diff read, 8-area consistency check, self-catch, comment, merge recommendation.

chrono-meta/forge-harness · 61 tokens

ai-driven-code-editor-cli

OpenCode AI - AI-driven code editor/IDE (CLI/TUI version of Cursor/Windsurf). Use when: (1) AI-assisted coding tasks, (2) Code refactoring with AI, (3) GitHub PR review/fixes, (4) Multi-file edits requiring context, (5) Running AI agents on codebases. NOT for: simple one-line ed…

rondoflow/rondoflow · 84 tokens

dos-verify-done-claims

Before accepting an agent's 'done / shipped / fixed' claim, verify it against ground truth (git ancestry + the commit's own diff) using the DOS kernel's dos verify and dos commit-audit — never the agent's own narration.

anthony-chaudhary/dos-kernel · 61 tokens

Tashan-TopicLab: Skill for Cursor