jayli / jayli/mc-lite

qwen3.5费用

Open
#31 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

任务:给工程补充用例

用量:

Image

费用:

```
┌─────────────────────────────────────────────────────────────┐
│ 费用计算明细 │
├─────────────────────────────────────────────────────────────┤
│ Input : 0.0195 × 0.8 = 0.0156 元 │
│ Output : 0.0752 × 0.8 = 0.0602 元 │
│ Cache Read : 9.4 × 0.16 = 1.5040 元 │
│ Cache Write : 0.8793 × 0.8 = 0.7034 元 │
├─────────────────────────────────────────────────────────────┤
│ 总计费用 : = 2.2832 元 │
└─────────────────────────────────────────────────────────────┘

费用占比饼图:

Cache Read ████████████████████████████████ 65.9% (1.50 元)
Cache Write ████████████████ 30.8% (0.70 元)
Output ███ 2.6% (0.06 元)
Input █ 0.7% (0.02 元)

```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue provides a Qwen3.5 usage example and cost breakdown but names no file, test, or entry point. First inspect the repository structure and existing use cases, then add the matching case; it is done when the example and its cost calculation are represented in the project.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.